Systems Analysis and Design II Coursework Assignment Birkbeck, University of London Academic Year 2023/24 Deadline: 17/03/2024, 23:55 GMT General information • The coursework assignments for Systems Analysis and Design II will be graded with a mark between 0 and 100; the coursework mark counts for 50% of the total grade for this module. The remaining 50% will result from the mark of a written examination. ⚫ The coursework is to be completed in five parts and must be submitted during term time by the 17th of March, 2024. The following table shows the marks awarded as well as a suggested completion date for each part. Part no. Topic Suggested date Marks 1 Requirements analysis 14/02/2024 20 2 Responsibilities 21/02/2024 20 3 Operation Specification 28/02/2024 20 4 Persistence Design 06/03/2024 20 5 UI Design 13/03/2024 20 • You should follow carefully the instructions regarding each part, including those regarding the formatting (which are not difficult to follow). • The coursework report (for all five parts) must be submitted in a single PDF file (no Microsoft Word or other formats). The file must be named according to the following template: surname_name_id.pdf. • All late submissions will be capped according to the regulations, unless a Mitigating Circumstances claim is approved. You are strongly encouraged not to submit at the very last minute, so as to avoid technical problems which may cause a late submission. • Notice that the completion dates for the individual parts are only recom- mended; the only strict deadline is the one for the coursework submis- sion. 1 0 Introduction In this coursework you will go through various design phases of an object- oriented information system of your choice. Examples are shown on the Moodle page of the module. You must write the requirements by yourself, working on a real-world or a realistic domain of interest. For the purpose of this coursework, your requirements will be simpler than those of most real-world systems: you must have at least 7 classes in the essential class diagram of Part 1. To produce UML diagrams, you can use any tool, including simple drawing software or even drawing by hand. For example, an open-source UML tool is StarUML. 1 Requirements Analysis and Conceptual Modelling In this part you must produce the following design artifacts. a. A set of requirements in natural language (English). This is a short text explaining what your system needs to do. The text needs to be concise and rigorous. (10 marks) b. An essential class diagram in UML. The essential class diagram identifies the entities (with one class per entity) in the domain of interest, as well as the relationships among them (represented as associations with their- multiplicities), but leaving out the operations and the attributes. This constitutes a high-level conceptual model of your system, representing the domain of interest of said system. (10 marks) • This part awards up to 20 marks. The suggested completion date for this part is the 14th of February, 2024. 2 Responsibilities with CRC Cards In this part of the coursework you identify the responsibilities of each class with respect to the use cases of the system. You must produce the following design artifacts. a. A use case diagram in UML. This should be derived straight from the functional part of the requirements you wrote in Part 1. (10 marks) b. CRC cards for all classes (entities) in the essential class diagram you wrote in Part 1. The cards are produced by “crossing” the use case diagram with the essential class diagram. (10 marks) This part awards up to 20 marks. • The suggested completion date for this part is the 21st of February, 2024. 2 3 Operation Specification This part concerns with the design of the functional part of your system. You must produce the following. a. The list of operations to be implemented in the system, at a finer grain than the use cases. Each operation will be documented by a few words that explain what the operation does. You should use names that are as explanatory as possible for the operations. (8 marks) b. The detailed specification of at least three, non-trivial operations. Each specification can be given in the form of a decision table, an activity diagram or in controlled English / pseudo-code. (12 marks) • This part awards up to 20 marks. • The suggested completion date for this part is the 28th of February, 2024. 4 Persistence Design In this part you design the part of your system that manages persistent data. This involves the persistent data themselves as well as the system in its object- oriented form. You must produce the following artifacts. a. The relational schema for the persistent data that your system needs to store. This will be a reflection mostly of the essential class diagram you produced in Part 1, obviously with the representation of all proper- ties/attributes of the classes (which are not represented yet in the essen- tial class diagram), whose information is found in the requirements set of (10 marks) Part 1. b. One broker class associated to an entity class of your choice among those in the essential class diagram. This must be represented in UML and must have individual operations, which will have to reflect the responsibilities of the entity class, among those identified in Parts 2 and 3, that operate on persistent data. (10 marks) • This part awards up to 20 marks. • The suggested completion date for this part is the 6th of March, 2024. 5 User Interface Design This part concerns with the user interface of your system. You do not have to deal with the architectural part here (see the MVC architecture), while you will instead focus on the UI and its appearance. You must produce the following artifacts. 3 a. An essential UI prototype for one major UI element of your system. This would be normally a paper-based prototype, with sticky notes moved around until UI elements are placed, without details, in the design of the Ul; in your case, you will include a figure (produced with tools of your choice, including hand-drawing) in the report. (10 marks) b. A high-level UI flow diagram related to the part of the UI necessary to one of the operations you have specified in Part 3. (10 marks) • This part awards up to 20 marks. • The suggested completion date for this part is the 13th of March, 2024. 4