Table of Contents - DSpace

More documents

Recommendations

Info

4.4.1 Collaboration DiagramsSeveral collaboration diagrams had been produced by the researcher during the stage ofuse case realization. These collaboration diagrams represent intermediate forms thatrealize their associated use cases.In the process of use case realization, the researcher was moving one step closer inconceiving the design model by identifying preliminary boundary class, entity class,control class and the interaction between all these classes within the given boundary ofeach collaboration diagram. Although the classes and interactions identified by theresearcher at this stage might be removed, replaced or further refined when thedevelopment process goes on, this information serves as a useful input in understandingthe behavioural aspects of the system requirements.Please note that in the collaboration diagrams shown in this section, each interactionbetween the use case actor and a class as well as the interaction between differentclasses is marked with a sequence number. This is to indicate the sequence of eachinteraction step to be executed under each collaboration scenario.The following subsections present the collaboration diagrams which were furtherdeveloped based on the input gathered from their corresponding use cases that had beendiscussed earlier in section 4.3.1 and section 4.3.2.72
4.4.1.1 Initiate User Session Collaboration DiagramFigure 4.8: Initiate user session collaboration diagramFigure 4.8 shows that the “Initiate User Session” use case has been evolved into acollaboration diagram. Use case actor and the other three classes, namely LoginUI class,AuthenticateAccount class and UserAccount class are collaborating among each otherin order to realize the “Initiate User Session” use case.Table 4.1 presents the role or class type held by each class in this collaboration diagram.Table 4.1: Classes in search colours collaboration diagramClass NameClass Type / RoleLoginUIBoundary ClassAuthenticateAccount Control ClassUserAccountEntity Class73
Page 2: 4.3.1 Use Case DiagramTo understand
Page 5 and 6: Use CaseGoal in ContextPrecondition
Page 7 and 8: Use CaseGoal in ContextPrecondition
Page 9 and 10: Alternative flows andexceptionsa) A
Page 11: 4.4 Use Case RealizationThe activit
Page 15 and 16: 4.4.1.3 Search Colours Collaboratio
Page 17 and 18: 4.4.1.5 Import Colours Collaboratio
Page 19 and 20: 4.4.2 Class Diagram4.4.2.1 Class Di
Page 21 and 22: Each colour is considered as an obj
Page 23 and 24: SearchColoursobserverilluminantL_va
Page 25 and 26: CompareColourscolourEncodingsIllumi
Page 27 and 28: InterfaceImportColourgetName ()getD
Page 29: 4.5 SummaryUse case driven object-o

Table of Contents - DSpace

Create successful ePaper yourself

Delete template?

Save as template?