Reference no: EM132177722
Question: System Analysis and Design
1. Explain the concept of "Alternative Matrix", and give an example of comparison using this form of Matrix to present three acquisition methods.
Note: Do not use the slides or Book example.
2. Suppose you are hired by a mega service company (e.g., Saudi Electricity Company). Your new role is the Chief IS Architect in charge of overseeing the establishment of the e-Business Infrastructure. The company decided to offer services through an Electronic Customer Relationship Management Channel or (e-CRM).
Here are the major requirements for the IS Architecture:
• The company has more than 25 Million customers including individuals, enterprises, and government institutes.
• Customers' records are stored into a DB2 server from IBM running MVS operating system.
• Employees and suppliers files are stored on an Oracle database to facilitate end-to-end eProcessing.
• Individual customers can access the new e-CRM using multiple platforms including mac, windows as client PCs, tablets and smart phones (iOS and Android) as handheld devices.
• Under no circumstance, shall the customers be allowed to access the back-end DB.
• There are 2 intermediate layers that reside between users and the enterprise IS.
• Customers are given the authority to establish/modify/configure services online, so all communication with customers are encrypted and strong authentication mechanism is in place.
Based on the given requirements, complete the diagram below with the necessary information, write the required information on the space provided.
3. Suppose you have to perform requirement analysis for a web-based forum system. There are only two type of users that interact with such a system: regular users and administrators. Each type of user has different set of responsibilities. Both type of users can sign in to the system, and part of signing in is an internal authentication process. Both type of users can also register with the system, which also uses internal authentication. After logging in, everyone can post new messages to the board, however only administrators can check statistics and create new threads. Regular users can send private messages to other users, while administrators do not have this ability.
Draw a use-case diagram that contains actors, use cases and their relationship from the scenario described above.
4. Consider an abstract class Duck, representing all available ducks. Every duck can quack and walk, which are their publicly accessible functionalities. While every duck walks the same way, they quack differently which makes quacking an abstract feature of a duck. Every duck has a weight which determines their ability to float, which can be checked by everybody through canFloat method. The weight of a duck can be set through a method available only for all concrete duck implementations. A rubber duck, a kind of a duck, has all the features of a duck (yes, it quacks), but when asked to walk - it acts differently, because a rubber duck can't walk, so it overrides a duck walk feature and does nothing. Another example of a duck is a wild duck that apart of quacking and walking, can also fly.
Draw a class diagram depicting classes, with names, attributes and methods along with proper relationship between classes. Skip constructors and destructors, but don't forget to annotate elements visibility using UML notation. For the actual attributes types or method signatures you can use Java notation, if you wish. Precede a name with a ‘/' symbol to indicate slanted (italicized) text.