Internet start-up company

Question 1 – Use Case Diagram a) Develop a use case diagram for TDNC, showin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing the primary and secondary actors, the use cases and the relationships between them. Pay attention to all actors, in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">includin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing the secondary actors. b) Develop use-case specifications for the use case “Add Note” and any related use-cases (i.e. such that have <<in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">include>>/<<extend>> or generalisation relationships with the use case “Add Note”). The specifications should cover all the options listed in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in the statement of requirements and should: •spell out the in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">interaction between the actors and the system related to addin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing a note, •send a confirmation usin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing an email confirmation with the note details, •cover the important exceptional circumstances (alternative flows) that might occur. Make plausible simplifyin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing assumptions if/when needed, but make sure these are clearly stated in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in your submission. Question 2: Analysis class diagram a) Develop an analysis class diagram for TDNC. Concentrate on the problem domain" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in classes, showin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing their attributes and important operations and the associations between the classes. •There is no need to in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">include type in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">information, get and set methods, or constructors. •Consider a min" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">inimal set of boundary and control classes that might be needed for use case realization. •Relationships: o Use associations where appropriate and in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">include in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in your models association or role names, direction arrows, and multiplicities, but don’t worry about navigability. o Use generalization/aggregation/composition where appropriate. o Don't bother with dependency relationships •Substantiate your answer usin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing one or more of the taught techniques for identifyin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing classes and their relationships: noun/verb analysis procedure, CRC cards, robustness analysis. You may use more than one technique in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in order to 4 improve your diagram, e.g. by discoverin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing new classes, attributes or operations, but usin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing more than one analysis method will not necessarily get you extra marks. Question 3: Use case realization (sequence diagram) Draw a sequence diagram that realizes the use case “Add Note”. The diagram should cover all possible branches, loops and alternatives that are documented in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in the use case specifications you develop in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in your answer to Q1b. Make sure that your sequence diagram is consistent with the class diagram you develop in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in your answer to Q2 and with the use case specifications you develop in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in your answer to Q1b.