project 1 – CE202 – 2017/18 – Production Line Requirements
Deadline: Wednesday 22nd November 2017, 11:59:59
Weight. 20% of final mark
What to submit:
Your project-related files should be included in a single .zip file (WinZip is installed and ready to use in all CS lab machines) and only the .zip file should be submitted. The name of the file should include your name and 'CE202', for example: SamLowryCE202.zip. The Zip file should include the following:
Document. Answers to all questions in the project should be combined in one file saved either in Microsoft Word (.doc) or Portable Document Format (.pdf) format. Text must be single-spaced 12 point Times font. Diagrams must be included in the document itself.
1. Use-cases [30%]
Read the Production Line Transcript document (which include some sample forms) that is included with this project.
This transcript is the first part of an interview that Rosanne Martel (RM) conducted with Hari Patel (HP), the Factory Manager in charge of FoodCo’s Beechfield factory.
(A) Draw a Use-Case DIAGRAM which shows the functionality that the system should provide that is used by the PRODUCTION LINE SUPERVISOR.
(B) Draw a Use-Case DIAGRAM which shows the functionality that the system should provide that is used by the PRODUCTION PLANNER
(C) Write Use-Case DESCRIPTIONS for the following use-cases:
0 START LINE RUN
0 RECORD EMPLOYEE JOINING THE LINE
0 RECORD EMPLOYEE LEAVING THE LINE
0 STOP LINE
0 RECORD LINE PROBLEM
0 END LINE RUN
(D) Identify CANDIDATE CLASSES that can be derived from the transcript and the use cases. For each candidate class determine whether it is a BOUNDARY, CONTROL or ENTITY class.
2. Communication diagrams [30%]
From these Use-Case DESCRIPTIONS and CANDIDATE CLASSES produce COMMUNICATION DIAGRAMS for EACH of the following use-cases:
0 START LINE RUN
0 RECORD EMPLOYEE JOINING THE LINE
0 RECORD EMPLOYEE LEAVING THE LINE
0 STOP LINE
0 RECORD LINE PROBLEM
0 END LINE RUN
There should be 1 communication diagram for each use-case (ie. 6 diagrams in total). Each communication diagram should match against the information provided in the relevant use-case description.
Your communication diagrams should be based on the candidate classes identified in part 1 above (you may need to revise your list of candidate classes as you work through the diagrams). Use class stereotypes in your diagrams to differentiate the roles that each object plays ie. Whether an object is a boundary, control or entity object.
Your communication diagrams should show the flow and order of messages passed between each object.
3. Class diagram [40%]
Produce a CLASS DIAGRAM for this system.
(A) First produce a draft analysis class diagram, initially showing only classes and associations.
(B) Then review your analysis class diagram and add any attributes and operations that you think are justified by your use cases. Make reasonable assumptions and add others that you think might be justified by other use cases not directly derived from the transcript.
(C) Write a short summary reviewing the communication and class diagrams. Particularly identify whether your diagrams are consistent with each other and the requirements analysis. Also describe whether you have had to impose additional requirements that were not originally provided in the transcript. If this is the case, explain what exactly are these requirements, and why you have had to impose these additional requirements.
