CS5002NI Software Engineering

T-14 Training Academy

20% Group Coursework
AY 2021-2022

Group Name:
SN Student Name (Section name) College ID University ID

1 Chanda Jaiswal (L2C7) NP01CP4S210170 20048875

2 Tista Dahal (L2C7) NP01CP4S210185 20049084

3 Nivi Shrestha(L2C7) NP01CP4S210173 20048941

4 Pranav Tamrakar(L2C7) NP01CP4S210187 20048952

5 Bansastha Sudhan Khadka(L2C7) NP01CP4S210188 20048860

I confirm that I understand my coursework needs to be submitted online via Google Classroom under the
relevant module page before the deadline for my assignment to be accepted and marked. I am fully
aware that late submissions will be treated as non-submission and a mark of zero will be awarded.
Table of Contents
1. Introduction ............................................................................................................... 1

1.1 Description of the business .................................................................................... 1

1.2 Aims and Objectives .............................................................................................. 1

1.3 Tools and Technique ............................................................................................. 2

2. Project Charter.......................................................................................................... 3

3. Software Requirement Specification ......................................................................... 6

4. Group Tasks ............................................................................................................. 6

4.1. Environmental Model Specification .................................................................... 6

4.1.1. Data Flow Diagram(DFD) ............................................................................ 7

4.1.1.1. Context Level Diagram.......................................................................... 8

4.1.1.2. Level 1 DFD .......................................................................................... 9

4.1.1.3. Level 2 DFD ........................................................................................ 10

4.2. Internal Model Specification for the system ...................................................... 12

4.2.1. Entity Relationship Diagram (ERD) ........................................................... 12

4.2.2. Data Dictionary .......................................................................................... 13

4.2.2.1. Data Dictionary for T-14 Training Academy ............................................ 14

4.2.3. Process Specifications............................................................................... 16

4.3. Design Specifications ....................................................................................... 22

4.3.1. Structure Chart .......................................................................................... 22

4.4. Assignment Diary ............................................................................................. 23

4.4.1. Group Member Details and Responsibilities .............................................. 23

4.4.2. Meeting Details .......................................................................................... 25

4.4.3. Assumptions .............................................................................................. 27

5. Individual Tasks ...................................................................................................... 28

5.1. Register membership (Tista Dahal).................................................................. 28

5.1.1. Environmental Model Specification ............................................................ 28

5.1.1.1. Context Level Diagram ........................................................................... 28

5.1.2. Internal Model Specification .......................................................................... 28

5.1.2.1. Level 1 DFD............................................................................................ 28

5.1.2.2. Level 2 DFD............................................................................................ 29

5.1.3. Design Specification ..................................................................................... 30

5.1.3.1. Structure Chart ....................................................................................... 30

5.1.3.2. Module Specifications ............................................................................. 32

5.2. Enroll Staff Members(Bansastha Sudan Khadka) ............................................ 33

5.2.1. Environmental Model Specification ............................................................ 33

5.2.1.1. Context Level Diagram ........................................................................... 33

5.2.2. Internal Model Specification .......................................................................... 33

5.2.2.1. Level 1 DFD............................................................................................ 33

5.2.2.2. Level 2 DFD............................................................................................ 34

5.2.3. Design Specification ..................................................................................... 35

5.2.3.1. Structure Chart ....................................................................................... 35

5.2.3.2. Module Specifications............................................................................. 36

5.3. Purchase Football Kits (Chanda Jaiswal) ......................................................... 37

5.3.1. Environmental Model Specification ............................................................ 37

5.3.1.1. Context Level Diagram ........................................................................... 37

5.3.2. Internal Model Specification .......................................................................... 38

5.3.2.1. Level 1 DFD............................................................................................ 38

5.3.2.2. Level 2 DFD............................................................................................ 39

5.3.3. Design Specification ..................................................................................... 39

 5.3.3.1. Structure Chart ....................................................................................... 39

5.3.3.2. Module Specifications ............................................................................. 41

5.4. Report Preparation (Pranav Tamrakar) ............................................................ 42

5.4.1. Environmental Model Specification ............................................................ 42

5.4.1.1. Context Level Diagram ........................................................................... 42

5.4.2. Internal Model Specification .......................................................................... 42

5.4.2.1. Level 1 DFD............................................................................................ 42

5.4.2.2. Level 2 DFD............................................................................................ 43

5.4.3. Design Specification ..................................................................................... 43

5.4.3.1. Structure Chart ....................................................................................... 43

5.4.3.2. Module Specifications............................................................................. 44

5.5. Take a mock exam(Nivi Shrestha) ................................................................... 45

5.5.1. Environmental Model Specification ............................................................ 45

5.5.1.1. Context Level Diagram ........................................................................... 45

5.5.2. Internal Model Specification .......................................................................... 45

5.5.2.1. Level 1 DFD............................................................................................ 45

5.5.2.2. Level 2 DFD............................................................................................ 46

5.5.3. Design Specification ..................................................................................... 47

5.5.3.1. Structure Chart ....................................................................................... 47

5.5.3.2. Module Specifications ............................................................................. 48

6. Summary ................................................................................................................ 49

7. References ............................................................................................................. 51

8. Appendix: (SRS Document) ....................................................................................... i

List of Figures
Figure 1: Context Level DFD of T-14 Training Academy ................................................ 8
Figure 2: Level 1 DFD ..................................................................................................... 9
Figure 3: Level 2 DFD of report preparation .................................................................. 10
Figure 4: Level 2 DFD of record purchase details of football kits .................................. 11
Figure 5: Level 2 DFD of conduct mock exam .............................................................. 11
Figure 6: Entity Relationship Diagram of T-14 Training Academy ................................. 13
Figure 7: Structure Chart of the T-14 Training Academy ............................................... 22
Figure 8 : Context level diagram for register membership ............................................. 28
Figure 9: Level 1 DFD for register membership ............................................................ 29
Figure 10: Level 2 DFD for register membership .......................................................... 30
Figure 11: Structure chart of register membership ........................................................ 31
Figure 12: Context level diagram for enroll staff members ............................................ 33
Figure 13: Level 1 DFD for enroll staff members ........................................................... 33
Figure 14: Level 2 DFD for enroll staff members ........................................................... 34
Figure 15: Structure chart of enroll staff members ........................................................ 35
Figure 16: Context level diagram for purchase football kits ........................................... 37
Figure 17: Level 1 DFD for purchase football kits ......................................................... 38
Figure 18: Level 2 DFD for purchase football kits ......................................................... 39
Figure 19: Structure chart for purchase football kits ...................................................... 40
Figure 20: Context level diagram for report preparation ................................................ 42
Figure 21: Level 1 DFD for report preparation ............................................................... 42
Figure 22: Level 2 DFD for report preparation ............................................................... 43
Figure 23: Structure chart for report preparation ........................................................... 43
Figure 24: Context level diagram for take mock exam .................................................. 45
Figure 25: Level 1 DFD for take mock exam ................................................................. 46
Figure 26: Level 2 DFD for take mock exam ................................................................. 46
Figure 27: Structure chart for take mock exam ............................................................. 47
List of Tables
Table 1: Project Charter .................................................................................................. 5
Table 2 : Group details and responsibilities................................................................... 24
Table 3: Group meeting log ........................................................................................... 26
Table 4: Module Specification for register membership................................................. 32
Table 5: Module Specification for enroll staff members ................................................. 36
Table 6: Module Specification for purchase football kits................................................ 41
Table 7: Module specification for report preparation ..................................................... 44
Table 8: Module Specification for take mock exam ....................................................... 48
CS5002NI Software Engineering

1. Introduction

1.1 Description of the business

The project required a group work of five members to work on the module 'Software
Engineering' coursework topic. This project is about the flaws in Training Academy, also
known as T-14 Training Academy. For this course, we are expected to access
requirements as a manager for a Training Academy to reduce flaws in a system that is
facing many challenges in preserving their records of players, membership registration,
enrolling personnel, and so on. A computerized system is established known as T-14
Training Academy. To complete our group assignment successfully and efficiently, we
had to organize a few meetings to gather the ideas and thoughts of all our group members
and implement them to establish a well-managed system.

Exam notice and announcements are posted on this system, as is the ability to enroll
staff, assist with mock exams, provide a discount on football kit purchases, generate a
report of preparation, examine test papers and practice test papers as needed, register
membership, and many other functions.

1.2 Aims and Objectives

The primary goal of this coursework is to comprehend and demonstrate our knowledge
of 'Software Engineering’. We learned to work in groups, adjust to everybody's opinion,
share ideas, and acknowledge our faults during this curriculum. Some others are as
follows:

1. The development of an application that will assist the T-14 training academy in
keeping track of their training records.
2. To efficiently assess the requirements and to address the challenges in a well-
organized manner.
3. Specifying and designing the substantial components of the system in accordance
with the structures approach.
4. To construct a DFD, an ER diagram, and a structured chart for functions based on
the information and attributes provided, and to integrate them into the system.

1
CS5002NI Software Engineering

1.3 Tools and Technique

This Coursework would not have been feasible without the assistance of software and
web applications such as Visio, Lucid-Chart, and Draw.io, as these tools are used to
create data flow diagrams, structure charts, ERDs, and context diagrams. The web
applications listed below were used to design and create all the DFD models and other
diagrams.

• Draw.io

The data flow diagram, ERD and structures chart were created using draw.io. Draw.io is
an application for especially constructing diagrams that permits to make the customizable
diagrams and for time managements (Mahendra, 2021). It can be used to make UML,
class diagrams, entity relations and many more.

• MS-Word

The report of the coursework was completed in MS-Word. It is a word processor

developed by Microsoft. It is widely used to prepare any type text documents. It is very
easier to work with MS-Word to prepare assigned report assignments. It has a lot of inbuilt
features like reference, insert, to design and many more which makes the work a lot
easier. It also makes converting files into .pdf document simple.

2
CS5002NI Software Engineering

2. Project Charter

Project Charter

Project Name: T-14 Training Academy

Project description: An online application for registering members, enrolling

staffs, conducting exams, generating report and so on .

Problem Statement: The business operations of T-14 Training Academy have

slowed as the Covid-19 has intensified. The process of
enrolling workers and registering members has been
simplified. The number of people taking the exam has
decreased and the chances to take physical exams are
less. Staff enrollment has dropped by up to 35%, while
member registration has dropped by up to 40%, resulting
in lower revenue.

Business Case: Benefits:

• Increased revenue.
• Increased enrollment.
• Increased number of exams.
• Increased registration.

Timescales:

• According to preliminary estimates, the system will

take 3 to 4 months to implement.

Total estimated cost = Rs. 30,500

Goal Statement: SMART objectives is a technique that may be used to

assist organizations and individuals set objectives in a
more effective and smooth way. The training academy

3
CS5002NI Software Engineering

followed SMART objective rules to set the goal for the

project charter:

• Specific: Increment in enrollment and registration

by 40% and 50% respectively.
• Measurable: Increment in revenue can be uplifted
within 5months with measured and appropriate
solutions.
• Achievable: Improvement upon 2021 performance
with 15% increase through new members, staff,
and trainers.
• Relevant: The engine that propels our profitability
is revenue.
• Time-based: Enhancement in the training
academy all aspects within a year with relevant
measure.

Timeline The time scheduled for different functions of the project

are :

Define/measure 06/03/2022

Analyze 06/08/2022

Improve/control 06/11/2022

The completion of project is scheduled for December

30,2022.

Scope The purchase handling tool will be used to request

purchase and provide discount to the members.

The project started with the development of system

context.

4
CS5002NI Software Engineering

The project designed meeting for the discussion on

project.

Risks Although the project appears to be simple, there are still

several unknowns around its implementation. There's
also the possibility that the project won't suit the needs of
the users. As a result, it is advised that all teams be
closely involved.

Goals of Implementation • Use of clean code.

• Use of refactoring code
• No reuse of code
• Use of maintainable code

Table 1: Project Charter

5
CS5002NI Software Engineering

3. Software Requirement Specification

The software's failure or success is largely determined by a technical document known
as the Software Requirement Specification (SRS) document, which contains all the
product's needs and features (Ali, et al., 2018).

The SRS document for the T-14 Training Academy is mentioned below (continue reading)

4. Group Tasks
4.1. Environmental Model Specification

Element of Model Representation Definition

Statement of Purpose Text Designing a system that provides

extensive information and reduces
present obstacles is the focus of this
project at the 'T-14 Training Site' of T-14
Training Academy.

System Text The app's working title was originally

slated as 'T-14 Training Academy.'
Making DFD diagrams before the
application is developed

General Description Text In this application, the role of players,

staff, and trainers is significant. In the T-
14 Training Application, they all play
critical roles and have special privileges.
Everyone here is connected to one
another.

Responsibilities Text The system being created will be able to

keep track of everything that the
Players, Staff, and Trainers are up to.

6
CS5002NI Software Engineering

Event List

• Membership registration in application for players

• Every age group has two training categories: Basic and Intermediate.
• The system allows trainers to create exam papers.
• New employees are entered into the systems.
• Members of professional football clubs get a preferential discount on things
listed in the system.
• Trainer can enter performance score.
• Trainer can provide reports on members' test performance.
• Admin should be allowed to post notices, results, etc.
• Members who desire to take intermediate training can take mock examinations
and see outcomes.

4.1.1. Data Flow Diagram(DFD)

In a structured approach, the DFD is the fundamental artifact that must be developed for
each system. It features a hierarchical structure that allows for several levels of
abstraction, which is useful in system design (Aleryani, 2016).

7
CS5002NI Software Engineering

4.1.1.1. Context Level Diagram

The context diagram (also known as a level 0 DFD) is the highest level in a data flow
diagram, containing only one process that represents the complete system and defines
the context and boundaries of the system to be depicted. It establishes the information
flows between the system and external entities (i.e., actors). In most requirements
documents, a context diagram is included. It must be read by all project stakeholders, so
it should be written in simple language that they can comprehend. The Context Diagram
illustrates the system in concern as a single high-level process, followed by the system's
connection with other external entities (systems, organizational groups, external data
stores, etc.) (ModernAnalyst, 2018).

Figure 1: Context Level DFD of T-14 Training Academy

8
CS5002NI Software Engineering

4.1.1.2. Level 1 DFD

The context diagram is split into numerous bubbles/processes in 1-level DFD. Level 1
depicts the flow of data between the various sections of the system and specifies internal
data stores that must be present for the system to function (Scheel, et al., 2015). The
essential functions of the system are highlighted at this level, and the high-level process
of 0-level DFD is broken down into subprocesses. Level 1 DFDs are still an overall review,
but they go far further than a setting graph.

Figure 2: Level 1 DFD

9
CS5002NI Software Engineering

4.1.1.3. Level 2 DFD

Level 2 DFD delves deeper into aspects of 1-level DFD. A level 2 data flow diagram (DFD)
depicts the processes that make up an information system in greater depth than a level
1 DFD. It can be used to plan or record a system's precise makeup (Tigosoftware, 2000).
It can be used to design or record specific/necessary details about how the system works.
It may be used to map out information flow, visualize a complete system, and share it with
stakeholders. Level 3 information stream graphs are point-by-point enough that additional
separation is unnecessary.

Figure 3: Level 2 DFD of report preparation

10
CS5002NI Software Engineering

Figure 4: Level 2 DFD of record purchase details of football kits

Figure 5: Level 2 DFD of conduct mock exam

11
CS5002NI Software Engineering

4.2. Internal Model Specification for the system

4.2.1. Entity Relationship Diagram (ERD)

An entity relationship diagram (ERD), often called an entity relationship model, is a

graphical depiction of relationships between people, objects, places, concepts, and
events in an information technology (IT) system. An ERD is a relational database that
uses data modeling approaches to assist design business processes and act as the
foundation. A prominent technique for designing data structures and database systems
is the entity-relationship diagram (ERD) (Chen & Li, 2009).

• Entity - An entity is any separate, identifiable object. It refers to major individuals,

organizations, systems, data chunks, or even specific system components.
Consider a university administrative system. It keeps track of students, teachers,
courses, and assessments. The database tables are student, teacher, course, and
exam. An entity is a record in the student table.

• Attribute - An entity's attributes are its properties. Let's revisit the university
administration system example. Student attributes include student id, name, age,
address, and GPA. The course entity has attributes like id, name, and duration.
Aside from that, the exam entity has features like exam number and date.

• Relationship - The term "relationship" is used to describe the interaction of two or

more substances. The exquisite stone-formed box engages with and speaks to the
senses. For instance, a representative works in a division, while an understudy
tries out for a certain course. In this context, the terms Works at and enrolls are
interchangeable.

12
CS5002NI Software Engineering

Figure 6: Entity Relationship Diagram of T-14 Training Academy

4.2.2. Data Dictionary

A Data Dictionary is a collection of names, meanings, and attributes related to data items
that are used or captured in a database, information system, or as part of a research
project. It includes instructions on data interpretation, permissible meanings, and
structure, as well as a description of the meanings and purposes of data items in the
context of a project. A Data Dictionary also includes metadata about the data bits it
contains. . A data-dictionary contains fields like name of entity, definition of entity, attribute
name and its description, datatype, length, and constraints like primary key or foreign key.
Therefore, a data dictionary is metadata database which is centralized (Bourne, 2014).

13
CS5002NI Software Engineering

4.2.2.1. Data Dictionary for T-14 Training Academy

Enroll staff = Command

Post exam notices and announcements = Command

Take mock exam = Command

Gives results = Command

Discount on purchase = Command

Register membership = Command

Purchase football kits = Command

Generate report = Command

Design test papers = Command

Report preparation = Command

Enter score = Command

Staff = StaffID + Staff_Name + Hire_Date

Notice = NoticeID + Announcement_Date + Title + StaffID

Trainer = TrainerID + Trainer_Name + Hire_Date

Testpapers = TestpapersID + Exam_Papers + Practice_Papers

Report = ReportID + MockExamID + TestpapersID + Score_No + Date

Score = Score_No + MemberID

Purchase = PurchaseID + Purchase_Item + Discount + MemberID + Purchase_Date

Members = MemberID + Member_Name + Registered_Name + Registration

Mock exam = MockExamID + Result

Staff info = {Enroll staff members + staff}*

14
CS5002NI Software Engineering

Notices info = {Post exam notices and announcements + notice}*

Mock exam info = {Take mock exam + mock exam}*

Test papers info = {Design exam test papers and practice test papers + testpapers}*

Members info = {Register membership + members}

Purchase info = {Purchase football kits + purchase}*

Report list = Report preparation + mock exam info + test papers info + members info +
score info

Generate report = Report list + Report info

Mock exam details = {Mock exam}

15
CS5002NI Software Engineering

4.2.3. Process Specifications

A process specification is a way for establishing, assessing, and clarifying the logic and
algorithms that are used to generate output data from process input data. Its goal is to
define and flow down regulatory and engineering requirements and procedures
(Techopedia, 2012).

The process specification of the processes in the diagrams are described below:

Process Number: 0.1

Process Name: Enroll staff members

Description: This process enroll the new staff members.

Input Data Flow: Enroll Staff members

Output Data Flow: Enroll Staff members

Detailed Logic: The logic for this process is as follows:

▪ Get staff details to enroll new members.

▪ Record the staff details information in the staff database.

Process Number: 0.2

Process Name: Record exam notices and announcements

Description: This process let staff to post exam notices and announcements.

Input Data Flow: Post exam notices and announcements

Output Data Flow: Post exam notices and announcements

Detailed Logic: The logic for this process is as follows:

▪ Record the exam notices and announcements in the notices

database.
▪ Command staff to post exam notices and announcements.

16
CS5002NI Software Engineering

Process Number: 0.3

Process Name: Conduct mock exam

Description: This process conduct mock exams for the member to take mock exam.

Input Data Flow: Take mock exam

Output Data Flow: Gives results

Detailed Logic: The logic for this process is as follows:

▪ Record the mock exam information in mock exam database.

▪ Conduct mock exam for the members to join intermediate training.

Process Number: 0.4

Process Name: Report Preparation

Description: This process prepares report of the registered members.

Input Data Flow: Report preparation command + Mock exam info + Test papers info +
Members info + Score info

Output Data Flow: Generate report

Detailed Logic: The logic for this process is as follows:

▪ Get mock exam record from mock exam database.

▪ Get test papers details from test papers database.
▪ Obtain members details from members database.
▪ Receive the score scored by the members from the score database.
▪ Filter the details obtained and prepare a report.

17
CS5002NI Software Engineering

Process Number: 0.5

Process Name: Provide score

Description: This process provides score to the members on basis of the exams.

Input Data Flow: Enter score

Output Data Flow: Enter score

Detailed Logic: The logic for this process is as follows:

▪ Store score scored details in score info database.

▪ Provides details of the score secured in exams.

Process Number: 0.6

Process Name: Record purchase details of football kits

Description: This process stores the purchase details of football kits.

Input Data Flow: Purchase football kits

Output Data Flow: Discount on purchase

Detailed Logic: The logic for this process is as follow:

▪ Record the purchase details in purchase info database.

Process Number: 0.7

Process Name: Register membership

Description: This process register the membership for the members.

Input Data Flow: Register membership

Output Data Flow: Register membership

Detailed Logic: The logic for this process is as follows:

▪ Record the details of members in a members info database.

▪ Get the members details to register the membership.

18
CS5002NI Software Engineering

Process Number: 0.8

Process Name: Design test papers

Description: This process designs the exam and practice test papers for the exam.

Input Data Flow: Design exam test papers and practice test papers

Output Data Flow: Design exam test papers and practice test papers

Detailed Logic: The logic for this process is as follows:

▪ Store exam and practice test papers in a test papers info database.

Process Number: 0.4.1

Process Name: Report Preparation

Description: This process prepares report of the registered members.

Input Data Flow: Report preparation command + Mock exam info + Test papers info +
Members info + Score info

Output Data Flow: Report list

Detailed Logic: The logic for this process is as follows:

▪ Get mock exam record from mock exam database.

▪ Get test papers details from test papers database.
▪ Obtain members details from members database.
▪ Receive the score scored by the members from the score database.
▪ Filter the details obtained and prepare a report.

19
CS5002NI Software Engineering

Process Number: 0.6.1

Process Name: Record purchase details of football kits

Description: This process record the purchase details of the football kits made in the
academy.

Input Data Flow: Purchase of football kits command + members info

Output Data Flow: Purchase details

Detailed Logic: The logic for this process is as follows:

▪ Get the record of the football kits purchased.

▪ Members record database is used to retrieve data about the
members who purchased football kits.

Process Number:0.6.2

Process Name: Provide discount

Description: This process provides discount to the members if any football kits is
purchased.

Input Data Flow: Purchase info

Output Data Flow: Discount on purchase

Detailed Logic: The logic for this process is as follows:

▪ Get details of the purchase made in the system.

▪ Obtain information about the members who made a purchase.
▪ Provide discount to the members who purchased any kits.

20
CS5002NI Software Engineering

Process Number: 0.3.1

Process Name: Conduct mock exam

Description: This process conducts mock exam for the members interested in joining
intermediate training.

Input Data Flow: Take mock exam

Output Data Flow: Mock exam details

Detailed Logic: The logic for this process is as follows:

▪ Get the details of the mock exam.

▪ Obtain the information about the members taking mock exam.
▪ Retrieve the information on the database.

Process Number: 0.3.2

Process Name: Give results

Description: This process gives results based on the mock exam given by the members.

Input Data Flow: Mock exam info

Output Data Flow: Give results

Detailed Logic: The logic for this process is as follows:

▪ Get the information about the mock exam from mock exam recorded
database.
▪ Provide results of the mock exam taken.

21
CS5002NI Software Engineering

4.3. Design Specifications

4.3.1. Structure Chart

Structure charts are designed to provide visual representations of the design's logical
processes (Morgan, 2003). The Structure Chart illustrates the hierarchical organization
of modules. When it comes to systems, it deconstructs them into the smallest functional
modules possible and then delves into the functions and sub-functions of each module in
more detail. The System Structure Diagram denotes the organization of the system
through the usage of black boxes (functionality of the system is known to the users but
inner details are unknown). The black boxes receive inputs and generate the
corresponding outputs.

Figure 7: Structure Chart of the T-14 Training Academy

22
CS5002NI Software Engineering

4.4. Assignment Diary

4.4.1. Group Member Details and Responsibilities

The coursework was distributed during Week 6 of 2nd Year's first semester. This course
was to be completed in a group of five people and was due on January 3 during Week
11. To complete this coursework, various procedures were made to resolve the issue and
submit the assignment on time.

To complete this coursework, several numbers were generated. Following confirmation

of group members, various meetings were held at various time intervals. At the
conference, the coursework was split among the members and the difficulties associated
with this work were discussed. Additionally, each member's particular task was divided.
After a few ups and downs, the coursework was submitted on time thanks to the members'
unity and cooperation. The following is a breakdown of the tasks assigned to group
members

Members Name Designation Tasks

Tista Dahal Manager Contributed to managing the group responsibilities.

Contributed to Entity relationship diagram designing.

Contributed to documenting process specification.

Individual work on Register membership.

Chanda Jaiswal Executive Contributed to executing the planned functions and

suggestions.

Contributed to designing DFD, and Structure chart.

Contributed to documenting project charter and SRS

document.

Individual work on Purchase football kits.

23
CS5002NI Software Engineering

Nivi Shrestha Documenter Contributed to documenting discussed topic and

providing materials to other group members.

Contributed to documenting data dictionary.

Contributed to keeping track of group meeting and

discussed details.

Individual work on Take a mock exam

Pranav Developer Contributed to developing the realistic scenario for

Tamrakar the task.

Contributed to documenting project charter.

Contributed to designing DFD levels.

Individual work on Report generation.

Bansastha QA Contributed to querying details of the project to make

Sudhan Khadka an effective and reliable project.

Contributed to documenting SRS document.

Contributed to documenting process specification.

Individual work on Enroll staff members.

Table 2 : Group details and responsibilities

24
CS5002NI Software Engineering

4.4.2. Meeting Details

We held several meetings to make this project better together. This meeting period of our
group members are shown below:

Date Time Mode Discussions

26/12/2021 10:30 AM - Offline The coursework was examined, and the work
1:30 PM was divided among the members.

27/12/2021 9:30 AM - Offline • The team came together to create

12:00 PM efficient and accurate data flow
diagrams.
• The issues of the balancing the data
flow diagram was discussed.
• Problem was faced during balancing of
the data flow diagram.
• The inflows and outflows were
reviewed briefly.
• The data flow diagram was successful
after several attempts.

28/12/2021 8:30 AM – Offline • Following the prior conversation, the

11:30 AM participants began working on their
individual parts of the group project.
• On the structural chart, the issue arose
once more.
• From the slides and online materials,
the members began to learn about the
structural chart.

25
CS5002NI Software Engineering

• After much deliberation, the structure

chart was ultimately completed, and
work on the next phase of the project
began.

30/12/2021 10:00 AM – Online • Individual tasks were divided, and

12:00 AM (Google participants choose which component
Meet) they would work on.
• The task to be completed for the
individual section was briefly
discussed.

02/01/2022 2:30 PM – 4:30 Online • After the group and individual tasks
PM were completed, an online meeting
(Google
was convened to go over everything.
Meet)
• The formatting was completed, and the
report was completed properly.

Table 3: Group meeting log

26
CS5002NI Software Engineering

4.4.3. Assumptions

While working on the group project, and designing DFDs few assumptions were made as
listed below:

• To generate the report, information is collected form the various databases like
members database, test papers database, mock exam database, score database
• While generating report, the report must specify the test papers and how much
marks is scored in them.
• The score database provides the details of the scores scored in the exams and
test papers while generating database.
• An outflow was created to balance the purchase record as discount is given on the
purchase of kits.
• The staff post exam notices and announcements, so the staff details is also
gathered from staff database.
• As a mock exam is conducted, a result is generated from the mock exam.
• When a mock exam is taken, the mock exam details is stored in a database and
the information from database is entered to give results.
• When the purchase details is recorded, the information is stored in a database and
with the help of database discount is provided.
• The report is prepared, and the report list is stored in the report info database and
the data from the database is used to generate report of members.

27
CS5002NI Software Engineering

5. Individual Tasks
5.1. Register membership (Tista Dahal)

Digital software for the T-14 Training Academy The T-14 Training Site includes a function
that enables the system to register students for membership. Members must supply
information such as their MemberID and Member Name, which is then authenticated or
checked by the system. After verification, the member's information is added to the
database, and the system successfully registers the member.

5.1.1. Environmental Model Specification

5.1.1.1. Context Level Diagram

This is the context diagram for the Membership Registration process. At this context level,
there is a process called Registration of membership, which is used by the system to
register members. Members can view the outcome of their registration.

Figure 8 : Context level diagram for register membership

5.1.2. Internal Model Specification

5.1.2.1. Level 1 DFD

This is the level 1 DFD diagram describing the process of registering as a member. The
System checks to see if the information provided by members is correct or not in this
section. Once the member's information has been validated, the member is registered
using the verified membership information and goes through the "Registration of
Membership" process, after which a MemberID is generated.

28
CS5002NI Software Engineering

Figure 9: Level 1 DFD for register membership

5.1.2.2. Level 2 DFD

You will need to utilize the level 2 DFD diagram to register for Membership. The process
of becoming a member is described in greater detail here. In this technique, a database
is built that contains information on the members that has been vetted and validated by
them. The information from verified members is successfully updated, and it is confirmed
a second time, following which they move to "Registration of Membership" to finish the
registration process. After registering, a member can check the status of other members
who have also registered.

29
CS5002NI Software Engineering

Figure 10: Level 2 DFD for register membership

5.1.3. Design Specification

5.1.3.1. Structure Chart

The general structure of the Register a member application is depicted in this diagram.
Procedures including registering a member, retrieving member information, confirming
member information, updating member information as needed, and displaying the
registered status are depicted in this diagram. It has two parameters: the Members Details
parameter and the Members Verified Details parameter. Members details are the details
about a member that are required for registration, whereas Validated Member Details are
the details about a member that the system has verified prior to registration. Following
that, the Verified Member details are added to the Member details, and the registration is
finished successfully. Members who have registered can access information about their
registration status.

30
CS5002NI Software Engineering

Figure 11: Structure chart of register membership

31
CS5002NI Software Engineering

5.1.3.2. Module Specifications

Name Register Membership

Purpose To register a member

Pseudocode DO

INPUT Member_name

INPUT MemberID

INPUT Registration

INPUT Registration_date

DO

IF (verified (Member_name, MemberID,

Registration, Registration_date))

END DO

DISPLAY Registered Member

DISPLAY (“MemberID:” + MemberID)

END DO

Input parameters Member details

Output parameters Registered MemberID

Global Variable None

Local Variable MemberID

Call Registration Result

Called by Member

Table 4: Module Specification for register membership

32
CS5002NI Software Engineering

5.2. Enroll Staff Members(Bansastha Sudhan Khadka)

The system enroll new staff members by using the staff details.
5.2.1. Environmental Model Specification

5.2.1.1. Context Level Diagram

The context diagram represents the staff enrollment using staff details by staff and the
registration is done by admin.

Figure 12: Context level diagram for enroll staff members

5.2.2. Internal Model Specification

5.2.2.1. Level 1 DFD

The level 1 diagram represnts the staff details being added in staff record database and
the information is further used to diaply registration status.

Figure 13: Level 1 DFD for enroll staff members

33
CS5002NI Software Engineering

5.2.2.2. Level 2 DFD

Figure 14: Level 2 DFD for enroll staff members

The level 2 diagram represents the enrollment of new staff by adding staff details and
recording in staff record and then displaying the registration status.

34
CS5002NI Software Engineering

5.2.3. Design Specification

5.2.3.1. Structure Chart

Figure 15: Structure chart of enroll staff members

35
CS5002NI Software Engineering

5.2.3.2. Module Specifications

Name Enroll staff members

Purpose To module obtains new staff enrolllment.

Pseudocode DO

INPUT staff details

DO

IF registration status is true

THAN generate StaffID

ELSE

Registration is done

END DO

DISPLAY staff record

END DO

Input Parameters Staff details

Output Parameters StaffID

Global Variables DB

Local Variables StaffID, Status

Calls none

Called by Enroll staff members

Table 5: Module Specification for enroll staff members

36
CS5002NI Software Engineering

5.3. Purchase Football Kits (Chanda Jaiswal)

The T-14 Academy also provides a special discount for academy members when
purchasing kits (Jerseys, Socks, Boots, training tracksuits, etc.) for the items specified in
the system, particularly the Jerseys of Professional Footballer Clubs.

5.3.1. Environmental Model Specification

5.3.1.1. Context Level Diagram

The context level diagram represents the purchase of football kits. Here, the members
makes a purchase of kits and the discount is applied by the admin who manages the
academy.

Figure 16: Context level diagram for purchase football kits

37
CS5002NI Software Engineering

5.3.2. Internal Model Specification

5.3.2.1. Level 1 DFD

The level 1 DFD for the purchase of kits represents the purchase of kits by a member.
Here, the purchase record of kits is stored in purchase details database which is used to
provide the special discount. Then , the discount information is stored in discount info
database.

Figure 17: Level 1 DFD for purchase football kits

38
CS5002NI Software Engineering

5.3.2.2. Level 2 DFD

The level 2 DFD represents the process of purchase of kits. The system check the
member registration status and if it is true then the members details is entered while
making a payment. Then the discount is applied for the members which is stored in
discount info database. The database details are further utilized to check the registration
status of the member.

Figure 18: Level 2 DFD for purchase football kits

5.3.3. Design Specification

5.3.3.1. Structure Chart

The structure chart represents for the module purchase football kits. The diagram
presents the module like purchase football kits which has two parameters member and
admin. The member purchase kits and the information is stored in purchase details info.
The stored information is provided to apply for discount and the member details are
entered and the discount is provided and information is stored. The admin checks the
registration status of the member and if the status is true then the members details is filled

39
CS5002NI Software Engineering

and payment id done with provided discount and the information finally gets recorded in
discount info database.

Figure 19: Structure chart for purchase football kits

40
CS5002NI Software Engineering

5.3.3.2. Module Specifications

Name Purchase football kits

Purpose To module obtains member registration

status details and provide discount to the
member and let member purchase football
kits.

Pseudocode DO
INPUT member details
INPUT purchase details
DO
IF registration status is true
THAN member details are
entered and discount is provided while
payment
ELSE
Registration is done
END DO
DISPLAY purchase information
DISPLAY discount information
END DO
Input Parameters Purchase details, Member details

Output Parameters Purchase info, Discount info

Global Variables DB

Local Variables MemberID, Status, PurchaseID

Calls Register membership

Called by Purchase football kits

Table 6: Module Specification for purchase football kits

41
CS5002NI Software Engineering

5.4. Report Preparation (Pranav Tamrakar)

The T-14 Training Academy generates a report of the exams conducted and progress.
5.4.1. Environmental Model Specification

5.4.1.1. Context Level Diagram

The context level diagram of Report preparation for the members based on the exams.

Figure 20: Context level diagram for report preparation

5.4.2. Internal Model Specification

5.4.2.1. Level 1 DFD

The level 1 diagram of the report preparation where generated report, customerID is
stored in customer record database and a report is prepared.

Figure 21: Level 1 DFD for report preparation

42
CS5002NI Software Engineering

5.4.2.2. Level 2 DFD

The level 2 represents the prepared report from the generated report, customerID,
customer Detail database and payment record database. Then the report detail is used
to display a report.

Figure 22: Level 2 DFD for report preparation

5.4.3. Design Specification

5.4.3.1. Structure Chart

Figure 23: Structure chart for report preparation

43
CS5002NI Software Engineering

5.4.3.2. Module Specifications

Name Report Preparation

Purpose The purpose of this module is to generate the

report of the customer. To create the report, it
collects the data from customer detail, payment
record and database.

Pseudocode DO
var
customer_detail=DB.get_customer_detail()
var
payment_record=DB.get_payment_record()
var customer_id =
customer_detail[‘customer_id’]
var report = generate_report(customer_detail,
payment_record)
Display(report)
END DO
Input Parameters customer_records

Output Parameters Customer_records

Global Variables DB

Local Variables customer_detail, payment_record,

customer_id, report

Calls Get customer detail, payment

record and generate report of the
customer

Called by Main

Table 7: Module specification for report preparation

44
CS5002NI Software Engineering

5.5. Take a mock exam(Nivi Shrestha)

The system takes mock exam to enroll members in intermediate training.

5.5.1. Environmental Model Specification

5.5.1.1. Context Level Diagram

The context level of this function represents the process to take mock exam.

Figure 24: Context level diagram for take mock exam

5.5.2. Internal Model Specification

5.5.2.1. Level 1 DFD

The level 1 DFD represents the process of taking the mock exam. The student registration
is done and the information is stored in question paper setup. Then the mock exam in
taken and result is generated.

45
CS5002NI Software Engineering

Figure 25: Level 1 DFD for take mock exam

5.5.2.2. Level 2 DFD

The level 2 represents the conduction of mock exam and information stored in the
database.

Figure 26: Level 2 DFD for take mock exam

46
CS5002NI Software Engineering

5.5.3. Design Specification

5.5.3.1. Structure Chart

Figure 27: Structure chart for take mock exam

47
CS5002NI Software Engineering

5.5.3.2. Module Specifications

Name Take a mock exam

Purpose This module is intended for members who

want to participate in Intermediate
training.

Pseudocode DO

var student_record =
DB.getStudentRecord()

var student_id = student_record[‘id’]

DB.de_register(student_id)

DISPLAY(‘Deregistration Successful’)

END DO

Input Parameters student_record

Output Parameters student_record

Global Variables DB

Local Variables student_record, student_id

Calls Get Student Detail, De-register, and

update student record

Called by Main

Table 8: Module Specification for take mock exam

48
CS5002NI Software Engineering

6. Summary
The purpose of this coursework was to aid in the construction of the Training Academy's
management system. The facility's official name is the T-14 Training Academy. It allows
customers to take benefit of a wide range of services. While working on this project, we
ran into several issues. The two diagrams with the biggest concerns were the Data Flow
Diagram and the Structure Diagram. Because of our combined efforts, we were able to
overcome those obstacles, and we were successful in developing the Data Flow Diagram
and the Structure Diagram.

The project was prepared by sketching out the system's event list. We looked at what
kinds of features should be included in this system so that the user may enjoy and feel at
ease while using it. The concept diagram was then drawn. The Environmental Model
Specification is then completed. Then we began the Internal Model Specification, which
included the Data Flow Diagram (DFD) and the Entity Relationship Diagram (ERD)
(ERD). We then proceeded to Structure Chart. We were successful in drawing the Data
Flow Diagram and Structure Chart as per the project's requirements. We divided the
individual work among the several groups of participants after the group section was
completed. For functions such as registering members, enrolling staff members,
purchasing football kits, creating reports, and taking a mock exam, members designed
and presented their own Context Diagram, Data Flow Diagram, and Structure Chart.
Pseudocodes for each of these functions were also written separately. During this project,
various hurdles, or perhaps we should say difficulties, were faced. However, we were
able to overcome these obstacles and display everything in accordance with the system's
needs. We were able to handle all the challenges and obstacles thanks to the efforts of
our Group members. We used many internet research websites to look up all the difficult
phrases and ideas, such as DFD, ERD, and Structure Chart.

The group members were able to overcome all hurdles thanks to our members'
collaboration and hard work, as well as the help of lecturers and tutors. We learned how
to create a Concept Diagram, DFD, and Structure Chart in this assignment. This project
educated me about the software management specification despite its complexity. This
project taught us a variety of design abilities that will be beneficial in the future. We gained

49
CS5002NI Software Engineering

knowledge and experience because of our attempt and number of internet research
resources.

50
CS5002NI Software Engineering

7. References

Aleryani, A. Y., 2016. Comparative Study between Data Flow Diagram and Use Case
Diagram. International Journal of Scientific and Research Publications, 6(3), p. 124.
Ali, S. W., Ahmed, Q. A. & Shafi, I., 2018. Process to enhance the quality of software
requirement specification document. Lahore, 2018 International Conference on
Engineering and Emerging Technologies (ICEET).
Bhandakkanavar, R., 2018. Software Requirements Specification document with
example, s.l.: Krazytech.
Bourne, K., 2014. Data Dictionary. pp 329-343: In Application Administrators Handbook.
Chen, Y. L. & Li, Q., 2009. Entity-Relationship Diagram, Berlin: Springer.
Hedberg, T., Helu, M. & Newrock, M., 2017. Software Requirements Specification to
Distribute Manufacturing Data, USA: National Institute of Standards and Technology.
Mahendra, M., 2021. THE USE OF DRAW IO AS DIGITAL MIND MAP TO IMPROVE
STUDENTS’CREATIVITY AND STUDENTS’CONCEPT MASTERY IN LEARNING
HUMAN INFLUENCE ON ECOSYSTEM Doctoral dissertation, Universitas Pendidikan
Indonesia).. s.l.:s.n.
Malan, R. & Bredemeyer, D., 1999. Functional Requirements and Use Cases. Draft, p. 8.
ModernAnalyst, 2018. What is a Context Diagram and what are the benefits of creating
one?, s.l.: ModernAnalyst.
Morgan, K., 2003. Structured Design Methodologies. s.l.:Encyclopedia of Information
Systems.
Scheel, H. V. et al., 2015. Process Concept Evolution, s.l.: The Complete Business
Process Handbook.
Techopedia, 2012. Process Specification, s.l.: Techopedia.
Tigosoftware, 2000. Data Flow Diagrams (DFD) Explained. s.l.:Tigosoftware.

51
CS5002NI Software Engineering

8. Appendix: (SRS Document)

CS5002NI Software Engineering

Software Requirements
Specification

for

T-14 Training Academy

Prepared by Chanda Jaiswal

Tista Dahal

Bansastha Sudan Khadka

Nivi Shrestha

Pranav Tamrakar

Islington College

January 2, 2022
Table of Contents

1. Introduction……………………………………………………………………………….. 1

1.1 Purpose………………………………………………………………………………… 1

1.2 Document Conventions………………………………………………………………. 1

1.3 Intended Audience and Reading Suggestions……………………………………...1

1.4 Product Scope…………………………………………………………………………. 1

1.5 References…………………………………………………………………………….. 1

2. Overall Description………………………………………………………………………. 2

2.1 Product Perspective…………………………………………………………………... 2

2.2 Product Functions…………………………………………………………………….. 2

2.3 User Classes and Characteristics…………………………………………………… 3

2.4 Operating Environment……………………………………………………………….. 3

2.5 Design and Implementation Constraints……………………………………………. 3

3. External Interface Requirements……………………………………………………….. 4

3.1 User Interfaces………………………………………………………………………… 4

3.2 Hardware Interfaces………………………………………………………………….. 4

3.3 Software Interfaces ……………………………………………………………………4

3.4 Communications Interfaces………………………………………………………….. 4

4. System Features………………………………………………………………………….5

4.1 Description and Priority………………………………………………………………..5

4.2 Stimulus/Response Sequences………………………………………………………5

4.3 Functional Requirements…………………………………………………………….. 5

5. Other Nonfunctional Requirements…………………………………………………….. 7

5.1 Performance Requirements………………………………………………………….. 7

5.2 Safety Requirements…………………………………………………………………. 7

5.3 Security Requirements……………………………………………………………….. 7

 5.4 Software Quality Attributes…………………………………………………………… 7

5.5 Business Rules…………………………………………………………………………8

Appendix A: Analysis Models……………………………………………………………………. 8

Appendix B: Glossary…………………………………………………………………………….. 11

List of Figures

Figure 1: ERD Diagram .............................................................................................................. 2

Figure 2: Context Level Diagram ................................................................................................ 8
Figure 3: Level 1 DFD ................................................................................................................ 9
Figure 4: Level 2 DFD for report preparation .............................................................................10
Figure 5: Level 2 DFD for purchase details of football kits .........................................................10
Figure 6: Level 2 DFD for take a mock exam………………………………………………………..11
Software Requirements Specification for T-14 Training Academy

1. Introduction
1.1 Purpose

The purpose of this document is to provide an online system for registering members and
conducting assessments for the training academy's convenience.

1.2 Document Conventions

This document uses the following conventions:

DB Database
ER Entity Relationship

1.3 Intended Audience and Reading Suggestions

This project is a prototype for the training academy system, and it is only allowed on
college. This has been put in place with the help of college instructors. This project is
beneficial to both the training academy and the players.

1.4 Product Scope

The scope mostly relates to the T-14 Training product features for creating an online
system for future business operations. It focuses on the academy, its employees, trainers,
and the apps that enable online registration and other training programs. This SRS also
has the goal of defining the software requirements that will be developed. The standard
can be used to directly develop software requirements specifications or as a model for
defining a project- or organization-specific standard. It makes no mention of any method,
terminology, or tool for creating an SRS.

1.5 References
Bhandakkanavar, R., 2018. Software Requirements Specification document with
example, s.l.: Krazytech.

Hedberg, T., Helu, M. & Newrock, M., 2017. Software Requirements Specification to
Distribute Manufacturing Data, USA: National Institute of Standards and Technology.

IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements
Specifications. IEEE Computer Society, 1998.

Page |1
Software Requirements Specification for T-14 Training Academy

2. Overall Description
2.1 Product Perspective
The following information can be stored in the training academy:

• Training programs details:

It includes the training programs i.e., basic, and intermediate training programs.

• Member description:

It includes the member ID, name, address, phone number. This information is used to
register the member in the training academy.

• Staff description:

It includes the staff ID, name, address, contact. This information is used to enroll new
staff for the training academy who would manage the notices and announcement to
make.

• Trainer description:

It includes the trainer ID, name, address, contact number. This information is used to
contact the trainer when necessary as trainer is responsible for designing test papers
and giving scores to the members and generating report.

2.2 Product Functions

The product functions are shown in the below ER model:

Figure 28: ERD Diagram

Page |2
Software Requirements Specification for T-14 Training Academy

2.3 User Classes and Characteristics

Academic, professional and software developers are among the software system's
users. Web technologies should indeed be known to all users. Users may be familiar with
software development or manufacturing techniques, but they may not be familiar with
both. Users should, however, have a clear understanding on the tasks, activities, and
products of any process in which they are interested.

2.4 Operating Environment

The operating environment for the T-14 Training system is listed below:

• Distributed database
• Client/server system
• Operating system Windows
• Database : SQL+ Database
• Platform: Java/PHP

2.5 Design and Implementation Constraints

• All members, trainers, and staff must have their information saved in a database
that is available via the website.
• The online T-14 Academy is accessible 24 hours a day, 7 days a week.
• The response time should not take longer than 5 minutes.
• It must be user friendly that allows easy access to the client.
• Users can access the website from any computer with an internet connection and
the ability to browse the internet.
• The user should be able to search queries on the system.
• It will give a user detailed instruction on how to utilize and navigate the system.
• Implement the database using a centralized database management system at the
very least.

Page |3
Software Requirements Specification for T-14 Training Academy

3. External Interface Requirements

3.1 User Interfaces

The software makes it easier for the new users to use of the system by providing with
good graphical interface for front end of database. The software user interface must be
accessible with any browser that allows user to access like Internet Explorer. It can be
created by any tool or software package like MS Front Page.

3.2 Hardware Interfaces

The system must run over internet whose hardware is able to connect to the internet. The
system hardware requirements are as below:

• The processor should have Pentium 4.

• The processor should be greater than 1GHz.
• RAM should be greater than 1GB.
• Hard disk should be 40GB.

3.3 Software Interfaces

The system shall communicate with members for registration. It communicates trainer to
enter score and generate reports. It lets system to enroll staff members. The system
provides discount to the registered members. Microsoft visual studio is used for the front
end and SQL server is used for database.

3.4 Communications Interfaces

The HTTP protocol will be used by the system for internet connectivity, while the TCP/IP
protocol suite will be used for intranet communication. The port number used is 80. The
protocol used shall be HTTP. There shall be logical address of the system in IPv4 format.

Page |4
Software Requirements Specification for T-14 Training Academy

4. System Features
4.1 Description and Priority

The training academy maintains information on the training programs held, registration
membership, conduction of exams and report generation.

4.2 Stimulus/Response Sequences

• Search for training programs.

• Displays a detailed list for membership.

• Manages business operations.

4.3 Functional Requirements

The system's intended behavior is described by functional requirements. This behavior

could be expressed in terms of services, tasks, or functions that the system must
accomplish. Here, the functional requirements are :

• Enroll staff

The system shall allow to enroll new staff members.

The system shall record the new entries of staff and keep an updated record about them.

• Conduct mock exam

The system shall conduct a mock exam for the members to join the intermediate training.

The system shall allow to watch football related videos.

The system shall allow the users to take online mock exam.

• Design test papers

The system shall allow the trainers to design the exam and practice test papers.

The system shall allow the trainer to provide score on basis of the performance.

The system shall allow user to view the exam test papers.

The system shall allow the user to view practice test papers.

Page |5
Software Requirements Specification for T-14 Training Academy

• Register membership

The system shall user to register membership for interested one.

The system shall allow user to register for membership online.

The system shall keep record of the registered members.

• Record purchase details of football kits

The system shall record the purchase details of the members.

The system shall allow members to purchase football kits.

The system shall permit discount to the registered members on any purchase of football
kits.

The system shall record the football kits stock.

This system shall allow online payments for purchase made.

• Provides score

The system shall provide scores on basis of performance.

The system shall allow user to view the results.

The system shall allow the trainers to edit the results.

The system shall allow the trainers to update and provide scores to the members.

• Report preparation

The system shall allow the members to view the report.

The system shall allow the staff to generate the reports.

The system shall allow the trainers to edit the report and update it.

The system shall allow the report to have members, score, and test papers information.

Page |6
Software Requirements Specification for T-14 Training Academy

• Record exam notices and announcements

The system shall post exam notices.

The system shall post the recent announcements.

The system shall be updated about the exam notices and announcements.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
The system should be capable of handling number of training programs without issue.
The response time should be no longer than 5 minutes. The system should be updated
timely and the user should be provided with the recent fresh information.

5.2 Safety Requirements

The system should have a backup if any sudden damages happens to the database with
the major information. The backup should have an exact copy of the original information
and do not hamper any kind of further operations. Human users should not be harmed by
the system.

5.3 Security Requirements

Users who do not register should only be allowed to read information, not update, or
modify it, except for their personal data. Human users should not be harmed by the
system. At the very least, while defining access-level needs for the software system and
its associated services, the software development must follow the principle of least
privilege. Users having access restrictions should be included in the system.

5.4 Software Quality Attributes

The system should be available to the users anytime as many users make advance
registration. The system should provide correct information about the training and the
requirements to registration. The software should meet users need and should be
maintained appropriately

Page |7
Software Requirements Specification for T-14 Training Academy

5.5 Business Rules

The system architecture, design, implementation, and documentation should be built in a
way it minimizes the maintenance cost. The system should manage anticipated and
unexpected errors in a way that prevents data loss and long periods of inactivity. the
system should undergo various testing procedures to ensure the reliability of using the
system.

Appendix A: Analysis Models

Figure 29: Context Level Diagram

Page |8
Software Requirements Specification for T-14 Training Academy

Figure 30: Level 1 DFD

Page |9
Software Requirements Specification for T-14 Training Academy

Figure 31: Level 2 DFD for report preparation

Figure 32: Level 2 DFD for purchase details of football kits

P a g e | 10
Software Requirements Specification for T-14 Training Academy

Figure 33: Level 2 DFD for take a mock exam

Appendix B: Glossary
DB – Database

ERD – Entity Relationship Diagram

RAM – Random Access Memory

DFD – Data Flow Diagram

P a g e | 11