COMPANY’S LOGO

<Project Name>

Information System Analysis and Design Course

Group ##

Version X.X

MM/DD/YYYY
Instructor: Assoc. Prof. Ho Trung Thanh, Ph.D.
Group’s members:

Point / 10
NO. Full name Student ID (Individual Signature
Contribution)

5
Acknowledgements
Commitments
Abstract

The Executive Summary should provide a summary of the key points of the document: It
should include any relevant background information, the project approach/methodology,
major benefits upon project completion, major project milestones, and estimated
completion date. It should also include a brief description of the system components that
are illustrated in the designs, and it may briefly refer to development tools, and
platform/environment issues. The objective of the Information Systems Analysis and
Design stage is to determine what is required by understanding, analyzing and
documenting both the existing system (if any), understanding the client requirements for
the new system, and translating those requirements into design specifications for the new
system. An existing system may not necessarily be a computerized system – it could be
how they currently perform the tasks manually. The ISAD document, when signed off,
becomes a contract between you and your client, defining the functionality that you
undertake to provide. This Executive Summary should not exceed one page. Note: If
someone with no knowledge of your project reads only this Executive Summary, they
should have a clear overview of what the new system entails.
Table of Contents
List of Figures
Figure 1.1 (Under the figure)………………………………………………….5
Figure 2.1
List of Tables
Table 2.1 (Above the table)
List of Abbreviations

No. Abbreviations Meanings

GANTT and PERT Charts
Part 1. Introduction to the project

1.1 Introduction to the company

1.2 Overview of information system (related to the topic)
1.3
1.3 Business problems/Business needs
What does the company want the system to do? What is the problem they want to fix?
What are the different components needed for this system? And so on.

1.3.1 Business problem statement

Ex: Currently, ABC bank offers limited banking on weekdays (8 hours per day). This does
not provide enough service hours for the customers as the bank is not open in the
evenings as well as on the weekends. Moreover, when a customer calls the contact center,
it takes them at least 20 minutes before they can speak to an agent. This provides a bad
customer service experience. Moreover, each phone call that the customer makes, costs
us $3 per hour- which is a significant expense for the business.

1.3.2 Current system and system architecture/diagrams (As-is business/system)

Introduction
As-is current system (diagram) and description
As-is business process (BPMN) and description
Business problems discussion (more details)

1.4 Propose solutions

What are solutions? How do solutions solve the problems? What is the purpose of this
project? Who is the client and what do they want their system to be able to do? And so
on.

1.5 Deliverables (List and describe) of the project

1.6 Assumptions
What things were not specifically addressed in your design above? What assumptions are
you making in your design about the users or the technology they have?

Ex:
 Users have a computer or device with a browser.
 Users have an internet connection.
 Users have an email address for account creation.

1.7 System impacted

Ex: Online Banking capabilities will be added to customer facing website:
https://bank.com/en

1.8 Introduction to project’s methodologies (SDLC, Waterfall, Agile, Hybrid, or

others)
Part 2. Fact-finding and Requirements modeling for to-be system (new system)

2.1 Introduction to this part

2.2 Deliverables (List and describe) of this part
2.3 Introduction to techniques applied for Fact-finding and Requirements modeling
(Chapter 4…)

2.4 Business Requirement Documents

2.5 Systems Requirements Documents (reference Chapter 4)

2.5.1 Functional Requirements

Using the information from the scenario, think about the different functions the system
needs to provide. Each of your bullets should start with “The system shall . . .” For
example, one functional requirement might be, “The system shall validate user
credentials when logging in.”

Process-oriented
Information-oriented

2.5.2 Non-Functional Requirements

In this section, you will detail the different nonfunctional requirements for the system. You
will need to think about the different things that the system needs to function properly.
Performance Requirements
What environments (web-based, application, etc.) does this system need to run in? How
fast should the system run? How often should the system be updated?

Platform Constraints
What platforms (Windows, Unix, etc.) should the system run on? Does the back end
require any tools, such as a database, to support this application?

Accuracy and Precision

How will you distinguish between different users? Is the input case-sensitive? When
should the system inform the admin of a problem?

Adaptability
Can you make changes to the user (add/remove/modify) without changing code? How
will the system adapt to platform updates? What type of access does the IT admin need?

Security
What is required for the user to log in? How can you secure the connection or the data
exchange between the client and the server? What should happen to the account if there
is a “brute force” hacking attempt? What happens if the user forgets their password?
Part 3. Data and process modeling (reference Chapter 5)
3.1 Overview and purposes
3.2 Deliverables (List and describe) of this part
3.3 Business process Modeling (BPMN) (to-be system/process)
3.4. Requirement modeling by DFD (Data Flow Diagram)
3.4.1 Data sources, data flows, data store, data destinations, and process
3.4.2 Context diagram – Context level
3.4.3 Level 0 of DFD
3.4.4 Level 1 of DFD
3.5 Data Dictionary
Part 4. Object modeling (reference Chapter 6)
4.1 Overview and purposes
4.2 Deliverables (List and Describe) of this part
4.2 Scenarios, Models and Functionality
4.2.1 Use Case Diagram
4.2.2 Use Case Descriptions (User story)
4.3 Class Diagram
4.4 Sequence diagram
4.5 Activity Diagram
Part 5. System design (Chapter 8 & Chapter 9)

5.1 Database design (Chapter 9)

5.1.1 Overview and purpose
5.1.2 Deliverables
5.2.1 Identify entities, relationship, attributes, data types, and constrains
5.2.2 Entity Relationship Diagram
5.2.3 Data Normalization
5.2.4 Physical database in any DBMS (SQL server, SQlite or others)
5.2 User interface design (Reference Chapter 8) (Mockup)

What are the needs of the interface? Who are the different users for this interface? What
will each user need to be able to do through the interface? How will the user interact
with the interface (mobile, browser, etc.)?

5.2 User interface design (reference Figma or Axure RP 9 or 10)

5.2.1 Overview and purpose
5.2.2 Deliverables (List and Describe)
5.2.3 Creating Wireframes
5.2.4 Screen Mockups
5.2.5 Prototype

5.3 Validation (data, flow)

6 Project Plan
6.1 Work Breakdown Structure

Ex:

6.2 Project Milestones

 7. Lessons learnt

Issue / what did not work What the team should have
No. Lessons Learned
well done instead?

[Description] [Description] [Description]

[Description] [Description] [Description]

[Description] [Description] [Description]

[Description] [Description] [Description]

[Description] [Description] [Description]

No. What worked Well Lesson Learned (Best Practice)

[Description] [Description]

[Description] [Description]

[Description] [Description]

[Description] [Description]

[Description] [Description]

[Description] [Description]

[Description] [Description]

References
Appendix

Notes:
- Doing the project by group
- Duration: 7 weeks (May 6, 2025 à June 17, 2025 at 11:59 AM)
- Submission files: Word, PDF, Presentation and others (if any)
- Pages: 60-80 or more
- Must follow APA format for references and citations
- Should follow the Rubric in the syllabus to evaluate the project
- The score of group’s members of the final project may be different from because
of contribution, Q&A, preparation & presentation