Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

Q1- List the three design strategies, and give at least 2 advantages and 2 disad

ID: 3823607 • Letter: Q

Question

Q1- List the three design strategies, and give at least 2 advantages and 2 disadvantages of each.

Q2-

Differentiate between fat and thin clients.

State two advantages of using thin clients over fat clients.

Q3-

Suppose that your uncle is a real estate agent and he decided to have a web-site to list his available real estate properties. And use a laptop computer to show clients these properties. What hardware is needed to have a web-site and client to browse the properties on that web-site? How many (n-tired) computers are needed for this system? List at least one advantage for this new system?

Q4-

Discuss the major principles for User Interface Design?

Q5-

What are three main steps associated with building the (ERD), list these three steps?                                                    

Explain how do you represent, 1-to-1 (1:1), and 1-to-many relationship (1:N)   and many-to-many relationship (M:N) ?

Q6-

Case Study: describe using ERD diagram how the university can manage Building, Classroom, Course, students, and Instructors, each of which is a table that is drawn indicating Primary Key, and Foreign key. Then explains how the university can add a new course without conflicting with others courses’ time and classroom.

Notice: the relation between Course and Student is m-to-m because a Student may have more than one Course has more than one student.

Draw the ED-D using crows-feet notation. Show the entities and relationships between entities (Building, Classroom, Course, student, Instructor). Indicate the PK primary key, and FK foreign key in each table)


Explanation / Answer

Design Strategies-

There are2 approaches for developing any information, the top-down technique and also thebottom-up technique. whereas these approaches seem radically totally different, they share the common goal of utilising a system by describing all of the interaction between the processes.

Top – down style technique-

The top-down style technique starts from the overall and moves to the precise. In different words, you begin with a general plan of what's required for the system and so work your approach all the way down to the a lot of specific details of however the system can act. This method involves the identification of various entity varietiesand also the definition of every entity’s attributes.

Advantages-

• Your organization realizes a centered use of resources from the individual managed application.

• The 1st implementation becomes a showcase for the identity management resolution.

• When the phases square measure completed for the managed application, you've got enforced a deeper, a lot of mature implementation of the identity management resolution.

• Operation and maintenance resources don't seem to be at the start wedged as severely like the bottom-up approach.

Disadvantage-

• The resolution provides restricted coverage within the 1st phases.

• A marginal proportion of user accounts square measure managed within the 1st phases.

• You may need to develop custom adapters at associate degree early stage.

• The support and overall business won't understand the good thing about the answer as chop-chop.

• The implementation value is probably going to be higher.

Bottom – up style technique-

The bottom-up approach begins with the precise details and moves up to the overall. this is often done by 1stdistinctive knowledge|the info|the information} components (items) and so grouping them along in data sets. In different words, this technique 1st identifies the attributes, and so teams them to create entities.

Advantages-

• User and business awareness of the merchandise. advantages square measure realised within the early phases.

• You will replace several manual processes with early automation.

• You will implement secret management for an oversized range of users.

• You don't got to develop custom adapters within the early phases.

• Your organization broadens identity management skills and understanding throughout the primary section.

• Tivoli Identity Manager is introduced to your business with less intrusion to your operations.

Disadvantages-

• The structure structure you identify may need to be modified in an exceedingly later roll-out section.

• Because of the immediate changes to repository homeowners and also the user population, the roll-out can have the next impact earlier and need bigger cooperation.

• This strategy is driven by the present infrastructure rather than the business processes.

For other answers please provide as seprate questions

Thankyou