Objective: The aim of this project is to give the students an overview of an Object Oriented Analysis and Design techniques during the System development process. Outcomes: 1. Understanding the concept of visual modeling using UML. Use a CASE tool to construct appropriate analysis / design diagrams addressing a clearly defined problem. In solving project, a student must use Power Designer CASE tool, or any open source Case Tool. Using a paper and a pencil is not allowed at all. 2. Analyze and design a computer-based solution to a clearly defined problem using object oriented techniques. Project Task: Creating a System Requirement Specification (SRS) Document Students are expected to produce an analysis and design document that specifies the architecture of an information system for a fictitious/existent small business/organization. Such a document is known as a SRS Document. Groups of no more than three students will be expected to incrementally develop this document over the duration of the course. There are three main deliverables for the system proposal that are due at various stages of the course are all group-work based. Project is worth of 15% of your final marks Project Deadline: Project Deliverable 1: System Proposal (Introduction to Project and Requirements Specification) Project Deliverable 2: Final SRS Document (with Analysis & Design) 10 Marks Project Deliverable 3: Project Presentation 5 Marks Read the following guidelines, understands and present your response for the tasks assigned in a documented format. Note: Use an appropriate CASE tool for visual modeling (designing the diagrams) Project Report Contents: Based on your case study, the project report shall cover the following sections in the given order: Title Sheet Table of Contents Chapter 1: Introduction o Problem Description o System Capabilities o Business Benefits o Work Distribution Chapter 2: Requirements Specification Functional Non functional requirements, etc., Chapter 3: Use Case Diagrams o Design the Use Case diagram of the proposed system o Write Use Case documentation for some sample Use Case(s). Chapter 4: Design detailed class diagram with attributes, and behavior/operation, and an ERD. o Apply generalization, composition, aggregations and associations between classes. Chapter 5: Design Activity Diagram for the proposed system. Chapter 6: Design Swim Lane Diagram for the proposed system. Chapter 7: Design Sequence Diagram for the proposed system. Chapter 8: Database Design. o Identify attributes, datatype, data size, primary keys, foreign keys, Indices, integrity rules (constraints), and relationships (1-m, m-m, and 1-1). Chapter 9: Design Prototype / Sample Graphical User Interface for the proposed system. Chapter 10: Conclusion Chapter 11: Reference Chapter 12: Appendices Guidelines What to write in introduction? Work Distribution: (Chapter 1) WORK NAME Write what did each student work on. Write the student name Requirements (Chapter 2) Functional requirements: Describe all system requirements in enough detail for designers to design a system satisfying the requirements and testers to verify that the system satisfies requirements. Organize these requirements in a way that works best for your project (eg User Goal Technique) . Each requirement should be numbered (or uniquely identifiable) [List the functional requirements of the system.] Non-functional requirements: [List the non-functional requirements of the system categorized.]