Good Day!!i have final project on CIB 3103 - Object Oriented Analysis and Designi have chosse cinema booking systemplease see the attached files (Project template and Sample project)
HIGHER COLLEGES OF TECHNOLOGY
Student Name (Student ID)
Teacher Name:
Table of Contents
- Analysis of the system requirements for a business problem:
Write a paragraph (less than 100 words) to describe what deliverables are included in section1.
Introduction of the Problem Definition
Description of the system background
Write a paragraph (around 100 words) description of the business (organization), history of the business, location, market, and target customers for which the system is to be developed.
Description of the problem statement
Write (around 100 words) to describe of the problem faced by your organization for which you are proposing a solution.
Description of proposed solution
Write (less than 200 words) to describe your proposed solution to address the problem described above. Highlight the objective for proposing your system, the scope of your proposed solution, and the expected benefits of your proposed system to organization.
- Description of System Development Life Cycles used in project
Write a paragraph (100-150 words) to describe the system development lifecycle (SDLC) that you selected to develop your proposed system. The chosen project lifecycle must be suitable to your project case study. Explain reasons that made you decide to use the chosen system development lifecycle (SDLC). Use a modelling software to draw a diagram that describes the chosen project lifecycle (PLC) and include it in your answer.
Refer to pages 6 - 18 (System Development Methodologies) of chapter 1 of textbook to have a better understanding to system development lifecycles.
- Description of Fact-Finding Techniques used in requirement gathering process
Write a paragraph (100 words) detailing the fact-finding technique(s) you have used in your project for requirements gathering. Explain the main reasons that made you decide to use chosen technique(s). The chosen fact-finding technique(s) must be suitable to your project.
Write another paragraph (100 words) to explain the detailed process you did to perform fact-finding (e.g. for the case of interviews, explain who you will interview, how you will contact the interviewees, all the arrangements you did and the challenges you faced, etc.).
Include a copy of the Fact-Finding tool that you used (e.g. questionnaire / interview questions) in the project report appendix.
You do not need to conduct the actual interview and you may include information from your imagination but the included information should align with your project.
Refer to chapter3 (Requirements Determination) of textbook to have a better understanding to fact-finding techniques.
- List of User Requirements
Write a list of requirements you identified from information collected by the requirements gathering process that you performed in your project. If you have assumed the requirements (without requirement gathering process) you may make up the information but it need to be consistent with the fact-finding technique(s) you used in the previous section, as well as the given project. Include information about the functional, non-functional, and usability requirements in corresponding sub sections.
Refer to pages 114 - 117 of your textbook to have a better understanding to system requirements but your gathered requirements must be specific to your project only.
List of functional requirements
List here
List of non-functional requirements
List here
List of Usability requirements
List here
- Functional and Behavioral Model of the business system:
The second section is the “Creation of the functional and behavioral model for the system”. The detailed requirements for the section 2 are listed in the attached template. The section 2 will contain the following items:
Describe what (UML diagrams and other deliverables) constitute functional and behavioral model. Also describe what are subsections of sections 2 and what are they describing about your project.
Refer to pages 153- 154 of your textbook to have a better understanding functional model.
Refer to pages 236- 237 of your textbook to have a better understanding behavioral model.
- Create use case diagram of the system
Using a Modelling tool, create a Use Case Diagram for your project. Insert it in this location as an image. The Use Case Diagram must show the System Boundary, actors of the system, and use cases in your project. Actors should be associated with the use cases that they use. Where necessary, show includes, extends, generalization relationships between use cases, and generalization relationships between actors.
Refer chapter 4 of textbook for examples of use case diagrams but your use case diagram must be specific to your system functional requirements.
- Write use case description for use cases
Include a use case description document for use cases in use case diagram of your project included in previous section. Include only three main use cases from use case diagram of your project (main use case are those which represent core functionality of your system). Include relevant information such as name of use case, primary actor, stake holders and interests, brief description, trigger and its type, relationships, normal flow of events, sub flows, and alternative flows. The use case description document must be written based on a use case description template.
See page 176 of chapter 4 to get a template or use one which you used in class activities but your use case descriptions must be specific to your system functional requirements.
- Create activity diagram of the system
Using a modelling tool, create two activity diagrams for two main use cases in your project. Insert them in this location as image files. Your activity diagrams should describe which actors are doing which actions in the selected use cases. The activity diagrams should demonstrate your understanding of decision, merge, fork, join, and swim-lanes.
See examples of activity diagrams in chapter 4 of your textbook but your activity diagrams must be specific to your system functional requirements.
- Create behavioral model of the system
Using a modelling tool, create two behavioral models (Communication Diagram OR Sequence Diagram) for two scenarios of a main use case in your project. Insert them in this location as IMAGE files. Your behavioral models should describe the interaction between the objects of your system. The behavioral models should demonstrate your understanding of objects and messages between objects.
See examples of diagrams in chapter 6 of your textbook but your diagrams must be specific to your system functional requirements
- Design of the business system:
The third section is the “Design of the business system”. The detailed requirements for the section 3 are listed in the attached template. The section 3 will contain the following items:
- Design user interface screens for all components of the system
Using a prototyping software, design User Interface Storyboards for two main use case descriptions. Each storyboard should include 6-10 User Interface (UI) screens that represent actor actions and system response. Insert them in this location as IMAGE. Your UI screens must include menu bars and toolbars to enable the users to select commands in your screens.
Refer to chapter 10 of your textbook to better understand UI screen design but your screens must be specific to your project case study and consistent with the use case descriptions of your project.
Include at least 5 different screen controls that can be used on the UI screens you plan to design. Explain why you chose each control as in the following format:
| Screen Control | Use case ID | UI screen No | Reason to use specific screen control |
Table 1: screen controls and reason of their use
- Design relational database model for all components of the project
Map the class/object diagram of your system into a relational database design. Use the table format used in chapter 9 (page 387- 390) to detail the structure of your database tables. Your relational database design should be consistent with the classes/objects in your project class/object diagram.
Refer to Mapping Problem Doman Objects to RDBMS Format in chapter 9 of your textbook to get a better understanding of how to map classes to tables.
- Structural Model of the business system:
The forth section is the “creation of the structural model of the system”. The detailed requirements for the section 4 are listed in the attached template. The section 4 will contain the following items:
Using a modelling tool, create the analysis class diagram & object diagram (Structural Model) that describes the structural aspects of the system based on your functional models. Insert them in this location as image file. The structural diagrams should demonstrate your understanding of class & object names, attributes, attribute values, operations, association names and roles, multiplicity, super classes, subclasses, associations, aggregations and compositions. Add both class and object diagram in the corresponding sub section of this section.
See examples of class and object diagrams in chapters 5 of your textbook but your structural diagrams must be specific to your system.
- Create Class diagram of the system for all components of the system
Class diagram here.
- Create Object diagram of the system covering all components of the system
Object diagram here
- Reference Page
Include all the external references that you might have used. Use MLA or APA referencing style (Any One).
If you’re not aware of MLA or APA referencing style, refer to the library resources and librarians.
- Appendix Page(s).
- Appendix 1: Fact-finding tools
Include a hard copy of the fact-finding tool you have developed for requirements gathering.
- Other relevant appendices (if applicable).
Include any other documents related to the project.
