IEB20703 OOSAD

GROUP PROJECT
COURSE LEARNING OBJECTIVE FOR GROUP PROJECT

 CLO 2:
To analyze the information gathered to define user/system
requirements. (C4, PLO7)
 CLO3
To design the system models by using UML to develop a
small / medium scale of information system project based on
object-oriented system analysis and design approach. (C6,
PLO10)
TASK & DELIVERABLES

Num Task Deliverable Submission Week

1 Form a group of FIVE (5)
students. System Request Week 4 : Friday
2 Prepare System Request
3 Apply the analysis and design User Requirements Week 8 : Friday
process. Analysis Document
4 Design the prototype of the System Design Week 12 : Friday
system. Specification Document
PROJECT BRIEF

 Your team needs to identify a system that you would like to propose,
analyze the requirements and design throughout this semester. Your project
should address a real-world situation. The system has to support multiple
users or at least more than one type of user.
 Domain area : Health, Highway Maintenance, Food, Transportation, Library,
Tourism, Umrah, Schools, etc.
 The documentations for this project is divided into THREE (3) parts.
1. SYSTEM REQUEST

 A project initiation.
 A document that describes the business reasons for building a system and the
value that the system is expected to provide.
 Most system requests include five elements:
1. Project Sponsor
2. Business Need
3. Business Requirements
4. Business Value
5. Special Issue
1. SYSTEM REQUEST - EXPLANATION

Element Description Examples

Project Sponsor The person who initiates the project and who Vice President of Marketing,
serves as the primary point of contact for the Finance members,
project on the business side. CEO, IT Manager, etc.
Business Need Business related reason for initiating the Improve access to information,
project/system. Improve customer service
Business Requirements The business capabilities that the system will Capture customer demographic
provide/need to have. information,
Include product search activities
Business Value The benefits that the system will create for the RM 100, 000 cost savings from
organization. decrease supply cost.
2% increase in market share.
Special Issues Issues that are relevant to the implementation System needed in time before the
of the system, need to be known by the Hari Raya celebration 2024.
approval committee. Top level security in finance module.
EXAMPLE
2. USER REQUIREMENTS ANALYSIS DOCUMENTS

 The results of the requirements elicitation and the analysis activities are
documented in the User Requirements Analysis report. This document
completely describes the system in terms of functional and non-functional
requirements and serves as a contractual basis between the client and the
developer. The report must be written in the language of the client's domain of
business/expertise.
2. USER REQUIREMENTS ANALYSIS DOCUMENTS
2. USER REQUIREMENTS ANALYSIS DOCUMENTS
Num Steps Description

1 Gather requirements Involves the collection of requirements by communicating with the client or
stakeholders. Example data collected during this stage may include a
requirement for access to a product from a mobile device or a dashboard that
provides real-time metrics.

2 Analyze requirements Ensures that requirements are clear, complete, and consistent. During this
phase, the team will review all requirements to ensure each requirement
statement is clear. They want to verify that there are no contradictions and all
requirements align with the goal of the project. 

3 Requirements modeling The way a team will document the requirements. They will use different
formats that help visualize processes, detail use cases, or document
specifications. Modeling can use any of the six practical software requirement
analysis techniques.
4 Review Provides time to re-examine the process and resulting documents, and
identify areas for improvement.
2. USER REQUIREMENTS ANALYSIS DOCUMENTS
Content :
1. Current system
3. System models
2. Proposed system       3.5.1 Activity Diagram
2.1 Overview       3.5.2 Use-Case Description and Use-Case Diagram
2.2 Information and Requirements Gathering 3.5.3 Class Diagram
2.3 Functional Requirements 3.5.4 Sequence Diagram
        2.3.1
        2.3.2 Appendix : Gantt Chart
        2.3.3
        2.3.4
2.3.5
2.4 Non-functional Requirements
   2.4.1
   2.4.2
   2.4.3
2.4.4
2.4.5
3. SYSTEM DESIGN SPECIFICATION DOCUMENT

 System design describes how a system performs the requirements outlined in the Functional

Requirements. Depending on the system, this can include instructions on testing specific requirements,
configuration settings, or review of functions or code.

 A system design specification is a written document that explains your product and specifies what you

want it to perform as well as how the user should interact with it. While it may seem laborious to write
everything down, it is the most crucial thing you can do in the early stages of product design and
development. This is because the design specs direct the whole scope of your product development. 
3. SYSTEM DESIGN SPECIFICATION DOCUMENT

Content :
1. Design Consideration
1.1 Methodology
2. System Architecture
2.1 System Architecture Diagram
3. System Design
3.1 Database Design (Data Dictionary)
3.2 Storyboard
3.3 Graphical User Interface and Report Design
EXAMPLE : DEVELOPMENT METHODOLOGY
EXAMPLE : SYSTEM ARCHITECTURE
EXAMPLE : DATA DICTIONARY
EXAMPLE : STORYBOARD
EXAMPLE : GRAPHICAL USER INTERFACE DESIGN
EXAMPLE : REPORT DESIGN