2023

Programe Title BSc (Hons)/FdSc Computer Science

Module Title Systems Analysis and Design

Module Code 2066

ASSIGNMENT TITLE Design a Solution

Student Name

Student ID
1|Page

Table of Contents
PART A...........................................................................................................................................2

Task 1:..........................................................................................................................................2

1.1 The Waterfall Model.....................................................................................................2

1.2 Suitability to the above scenario:...........................................................................................3

1.2.1 Well-Defined and Stable Requirements:.........................................................................3

1.2.2 Linear and Sequential Process:........................................................................................3

1.2.3 Documentation-Driven Approach:..................................................................................3

1.2.4 Minimal Client Involvement during Development:........................................................4

1.2.5 Effective for Small to Medium-Sized Projects: -............................................................4

2. Agile Model:.....................................................................................................................4

2.1 Suitability to the above scenario:...........................................................................................4

2.1.1 Flexibility to Changing Requirements:...........................................................................5

2.1.2 Iterative Development:....................................................................................................5

2.1.3 Frequent Client Collaboration:........................................................................................5

2.1.4 Early and Incremental Delivery:.....................................................................................5

2.1.5 Adaptation to External Changes:.....................................................................................5

Task 2:..........................................................................................................................................6

1. Interview with the owner:.................................................................................................6

1.1 Observation of the Current Process:..............................................................................6

1.2 Questionnaire Completed by a Current User:...............................................................7

Task 3:..........................................................................................................................................8

1. Level 0 diagram:...............................................................................................................8

2. Level 1 DFD:....................................................................................................................9

3. Flow Chart:.....................................................................................................................10
2|Page

4. Data Dictionaries:...........................................................................................................10

5. System Requirements:.....................................................................................................11

6. Recommended Solution:.................................................................................................11

Task 4:........................................................................................................................................12

Detailed Design Documentation for Pass IT Driving School System....................................12

PART B.........................................................................................................................................15

Task 1:........................................................................................................................................15

1.Factors Affecting the Success and Failure of the New System for Pass IT Driving School:
15

Task 2:........................................................................................................................................18

7. Evaluation of the Pass IT Driving School System's Design in Relation to User

Requirements:.........................................................................................................................18

8. Possible Improvements and Further Developments:......................................................19

9. Conclusion:.....................................................................................................................20

References......................................................................................................................................21
3|Page

PART A

Task 1:

It appears that the Software Development Life Cycle (SDLC) approaches of the Waterfall Model
and the Agile Model are found to be more suited to the task of developing an automated
computerized system for Pass IT Driving School.

1.1 The Waterfall Model

The Waterfall model segments the project into distinct phases using a
linear, sequential methodology. This SDLC model can only be applied in this specific scenario
as the requirements are clear, fixed, and unambiguous. The scenario of the Pass IT driving school
system allows for an explicit product definition and no vague specifications. Furthermore, a
wealth of resources possessing the necessary experience to back the item in question are
available. Each student in this case has a distinct background and set of traits. The attributes that
follow serve as the foundation for their selection: the teacher, the students to whom they are
allocated, and the amount of time allocated.

Advantages Disadvantages
Sequential Structure: The Waterfall Model Rigidity: Less opportunity for change
is easy to use and understand due to its following the completion of a phase.
successive and linear methodology.
Document-Driven: Well-Suited for Small Long Delivery Time: As additional stages
Projects: The Waterfall Model is most are only started after the previous ones are
effective when applied to tasks whose needs finished, tasks may take more time to finish.
are well-defined and unlikely to change.
Well-Suited for Small-scale Projects: The
Waterfall Model is most effective when
applied to tasks whose needs are well-defined
and unlikely to change.
4|Page

1.2 Suitability to the above scenario:

In the present situation, waterfall model might prove appropriate given that its methodical
approach is feasible and the criteria of the system development of IP driving school scenario are
stable. Any prospective requirements shifts, though, need to be properly handled. These factors
make the Waterfall model a viable option when developing a computerized framework for Pass
IT driving school:

1.2.1. Precise and Stable Requirements:

The Waterfall model is effective when the specifications of the project are well-defined and
unlikely to shift over time. If the requirements for organizing activities, instructor projects, and
lesson reservations are precise and well-defined, the Waterfall technique could offer an
organized strategy to development within the framework of Pass IT driving school.

1.2.2. Linear and Sequential Approach:

The Waterfall model is a linear, sequential process in which every stage builds upon the previous
one. The driving school's methodical growth aligns well with its operational approach. The
requirements including the design, analysis and implementation, testing and maintenance, can all
be completed step-by-step during this phase.

1.2.3. A Documentation-Driven Method:

The incorporation of documentation is heavily emphasized at every stage of the the waterfall
method process. This is good for driving schools because it's important to have precise records of
student data, teacher details, and academic progress. Each step produces particular records that
guarantees the precise documentation of the system's operation and enhances interaction among
stakeholders.

1.2.4. Insignificant Client Involvement during Development Phase:

In most cases, the Waterfall approach requires minimal client involvement during the designing
phase. If the upper management of the driving school is happy with a thorough plan to the start
5|Page

and would rather not to be actively involved in the on a daily basis development tasks, then the
waterfall model works well with this approach.

1.2.5. Operative for Small to Medium-Sized Projects: -

The waterfall approach is a suitable fit for projects ranging from small to medium size with
specific and consistently designed requirements. The waterfall approach may be suitable if the IT
infrastructure of the IP driving school is not extremely complicated and is capable of being
planned, constructed, and put into operation in a methodical manner.

2. Agile Model:

Advantages Disadvantages
Flexibility: Because it allows for changes at Complexity: The project's additional
any stage, the agile model is appropriate for complexity may increase with their clients'
projects whose requirements fluctuate over continual involvement.
time. Documentation Challenges: Occasionally,
Iterative Development: It enables regular the focus on functional software leads to less
reassessment and modification as a thorough documentation.
response to feedback, enhancing the finished
product.
Client Collaboration: Consistent client
participation guarantees that the result lives
up to expectations.
6|Page

2.1. Suitability to the case of IP driving School:

The agile framework works well when prerequisites are more likely to change and ongoing client
interaction is required. Agile might prove helpful in the IP driving school scenario if there is a
high level of user engagement or if fast changes are required. The Agile methodology can offer
several advantages in the development of a computerized Pass IT driving school system.

2.1.1. Flexibility to Varying Requirements:

Regulations in the overall setting of driving schools may alter as a result of legislative
modifications, student selections, or technological developments. Agile methodology encourages
adaptability on all fronts, which facilitates task course modifications in response to changing
requirements.

2.1.2. Iterative Progress:

The design team can produce a working model more quickly because the agile model encourages
the changing design development cycles. This is in line with the IP Driving School's goal to
develop a structure that can be rapidly tested and enhanced to ensure that the finished product
meets the ever-changing needs of both teachers and students.

2.1.3. Recurrent Client Collaboration:

The standard feedback received from stakeholders and customers is highly valued in the agile
methodology. The leadership team, instructors, and even students at Pass IT Driving School
work closely together to ensure that the curriculum closely satisfies their demands and
requirements. It facilitates quicker adaptation in response to learning new details
and information.

2.1.4. Prompt and Incremental Delivery:

Agile model also encourages the development process to produce a minimum viable product
(MVP) quickly. This implies that necessary features can be introduced gradually, even if the
platform as a whole isn't equipped yet. This may entail adding important elements, such as
7|Page

assignments for instructors and, in the scenario of IP driving school, advance scheduling of
meetings.

2.1.5. Adaptation to External Shifts:

As the Pass IT driving school functions in an external setting with changing variables
such as modifications to driving regulations or testing procedures, the agile model' flexibility to
change allows the system to react promptly to shifts in the outside setting.

However, it's crucial to remember that Agile or any other iterative approaches might be
more appropriate if there's a chance that the external requirements are going to shift or if frequent
modifications are required in the wake of user feedback. While deciding between the
development methods of both the Waterfall and Agile models, it is important to take into account
the distinctive characteristics, preferences, and limitations of Pass IT driving school.

Task 2:

While gathering data for the driving school system's specifications guidelines, the application
of investigation methodologies is essential. Precise and meticulous data collection is essential to
the Pass IT Driving School system's achievement of success. For example, it is easier to
understand the needs and expectations of the owner when you speak with them face-to-face.
There are shortcomings and room for growth in the current process after a thorough analysis. By
filling out questionnaires, data regarding the desired outcomes as well as observations of current
8|Page

members of the system is gathered. This analysis examines the significance of different research
methodologies:

1. Conducting an Interview with the proprietor:

The proprietor of Pass IT Driving School possesses significant insight into the overarching aims,
functional protocols, and tactical priorities of the enterprise. Speaking with the company's owner
in person will help you grasp his goals for the computerized system, particular needs for his
company, and any particular worries.
Example:
During the discussion, it's crucial to ask the person in charge the following crucial questions: -

• What are the driving school's primary objectives?

• How will the computerized framework improve upon the current methods of operation, in
your opinion?
• Are there particular functions or features that you would prefer?

1.1 An Observation Run of the Current Process:

Observing of the driving school's existing procedures can provide valuable hands-on insight into
daily operations, possible obstacles, and domains that need improvement. It provides context for
the system specifications and ensures that the generated solution complies with the existing
workflow.
Example: For an overview of how the courses are organized and documented, an observer could
visit the driving school's office and track the teachers in action. This could draw attention to
manual processes, ineffectiveness, or communication failures that require fixing in the automated
system.

1.2 A Current User's Completed Questionnaire:

It is fairly possible to obtain a sense of the requirements, issues, and perspectives of those who
additionally are regularly employing the system by distributing questionnaires to current users,
such as driving trainers or employees in offices.

For instance:
9|Page

 On a survey, driving instructors might be asked a number of kinds of queries: - How do

you plan and coordinate your driving courses these days?
 What challenges are there that you face when it comes to keeping an eye on how your
pupils are making progress?
 Which attributes do you believe could increase your output?

Conclusion:

To sum up, a combination of questionnaires, interviews, and in-person observations ensures a

complete and accurate understanding of the requirements of the Pass IT Driving School system,
laying the groundwork for a functional and user-friendly computerized solution.

Task 3:

Following the initial inquiry and the company's leaders' endorsement of the recommendation, the
design proof is as follows. Following the initial inquiry, once the business administrators have
evaluated and accepted the proposal, you must produce thorough documentation on design. But
this will depend on the approach that is used and should include:

1. Level 0 diagram:
10 | P a g e

Administration

Test Organisation Process progress reporting process

Student details lesson booking process lesson details
instructor avalaibility test details

Lesson Details

Students Instructor
Entity: IP Driving
School System

Fig.1.1.
11 | P a g e

Level 1 DFD:

Fig.1.2. Detailed Design Documentation for Pass IT Driving School System

 12 | P a g e

Flow Chart:

Data Dictionaries:

Student Data Lesson Data Instructor Data Lesson Progress Data

Data Name: Student Data Name: Data Name: Instructor Data Name: Objectives
Name Lesson_Type Name Covered
Type: Text Type: Dropdown Type: Text Type: Text
Field Size: 50 characters Field Size: Not Field Size: 50 characters Field Size: 100 characters
Source: Provided by the applicable Source: Selected by the Source: Entered by the
student Source: Selected by the student or assigned by the instructor
Input Method: Text student system Input Method: Text input
input Input Method: Input Method: Dropdown
Validation Checks: Optional
Validation Checks: Dropdown selection selection or system
field (alphanumeric characters
Required field, Validation Checks: assignment
only
alphanumeric characters Required field, Validation Checks:
 13 | P a g e

only predefined options only Required field,

alphanumeric characters
only

System Requirements:

Inputs Processes Output Scope Constraints

Student details Validate Student Confirmed Lesson booking, Availability of
(name, contact Details. lesson details. instructor instructors.
information). Check Instructor Progress assignment, Timely
Lesson Availability. updates. progress scheduling of
preferences Record Lesson tracking. lessons.
(type, preferred Details.
instructor).
Instructor
details.

Recommendation of a Solution:

 Provide a web application with a responsive design.

 Create a database to store records of students and lessons.
 Combine user-friendly interfaces for instructors and students.
 Use secure login processes to protect sensitive data.
 Carry out extensive testing to ensure that the system is accurate and reliable.
Conclusion:
14 | P a g e

This thorough design documentation, which includes data dictionaries, flow charts, data flow
diagrams, and system requirements, offers a thorough overview of the Pass IT Driving School
system. The suggested approach centers on an intuitive and effective web-based application to
optimise the scheduling of lessons, assigning tasks to instructors, and monitoring student
progress.

Task 4:

3. Detailed Design Documentation for Pass IT Driving School System

1. Data Entry Forms:

a. Lesson Booking Form:
Layout and Structure: - The design is basic and user-friendly, and the parts are
labelled.
- There are fields for the student's name, email address,
preferred teacher, lesson type, day, and time.
- Dropdown menus to facilitate selecting the teacher and
type of instruction.
- A straightforward calendar picker for inputting the time
and date.
Proposed Fields: 1. Student Name:
2. Contact Details
3. Lesson Type (Introductory, Standard, Pass Plus, Driving
Test)
4. Preferred Instructor
5. Date/Time
Data Entry Methods: - Name and text entry contact details are entered.
- Dropdown menus for lesson types and instructor selection
A calendar picker for choosing the day and time.

b. Form for Lesson Progress:

Organization and Framework - a clean design with sections for updating
15 | P a g e

personal data and student accomplishments.

- spaces for the teacher's notes, the lesson's
addressed objectives, the date, and the time.
- a clear border demarcating completed from
upcoming classes..
Proposed Fields Student Name
Lesson Date/Time
Objectives Covered
Instructor Comments
Data Entry Methods: Text input for lesson objectives and
comments.
Dropdown menus for lesson selection.
Automatic timestamp for date/time.

2. Report Forms:
a. Weekly Lesson Timetable Report:
Layout and Structure:
a table with columns for the instructor's identity, the time and date, and the kind of lesson.
Color coding makes it simple to identify different lesson types.
a rundown of every lesson that each teacher has ever taught.
Proposed Fields:
1. Instructor Name
2. Lesson Date
3. Lesson Type
b. Student Progress Report:
Layout and Structure:
A comprehensive report that includes sections on how students' individual progress and details.
Visual illustrative aids for a concise synopsis, such as charts.
An explanation of the classes that have ended and the schedule of events.
Proposed Fields:
16 | P a g e

i. Student Name
ii. Total Lessons Completed
iii. Current Lesson Schedule
iv. Visual Progress Chart
Hardware and Software Requirements:
a. Hardware Requirements:
Computing Devices:

• Office personnel use desktop PCs.

• iPads for teachers to conduct classes while they're on the road.
Printers:

• Made hard copies of documents and reports using this method.

Network Infrastructure:

• Quick internet access to enable cloud storage.

b. Software Requirements:
Operating System (OS):
The operating system (OS) that office computers run
- Multi-platform application development for tablets.
Database Management:
Lesson details and student's data are kept in a database with relational structure.
Development Tools:
Software development's Integrated Development Environment (IDE).
Security Software:
Software firewalls and antivirus programs protect data.
User Interface Framework:

• Cross-platform interoperability through flexible web design.

• The objectives of this thorough documentation of design are brevity, accessibility, and
efficient management of the activities of driving school activities.
17 | P a g e

PART B

Task 1:

7 Factors Affecting the Success and Failure of the New System for Pass IT
Driving School:

 Risk Associated with On-time and Budget friendly Delivery of Tasks:

Success factors:

Project Planning: Risks that are related to obstacles like developmental impediments and
budget overruns could be mitigated with a comprehensive plan of the existing project including
task itemizations, timetables, and resource allocation of resources.

Systematic Monitoring and Control: When the project's progress is regularly tracked, it is
possible to identify possible problems early and subsequently determine to take prompt
corrective action.

Contingency Planning: By bringing contingencies in effect, project timetables and budgets are
less vulnerable to the effects of unforeseen events or complications.

Failure Factors:
18 | P a g e

Inaccurate Estimations: Unexpected obstacles, erroneous task or material estimations, and

complications regarding the timelines can all lead to budget fluctuations and delays.

Unattended Risk Management: If potential risks are ignored or a strategy to mar the risk
management is not used, unanticipated setbacks may occur.

Scope creep: Expanding the project's accomplishing parameters without completing a

comprehensive assessment may lead to increased costs and the amount of work.

 Expenditure, Time Constraints and Organisational Policies:

Success Factors:

Total compliance with the budget allotted by using effective cost-control strategies.

It takes successful resource administration and task supervision to complete projects by the
appointed time.

Making certain that the rules and regulations of the company are followed when developing new
systems.

Failure Factors:

Insufficient resource distribution: Absence of staff and technology shortages could possibly
cause delays.

A misalignment of the scope: Misunderstandings and issues in failing to comply may stem from
a venture's opportunity that doesn't fall in line with the company's standards.

Inefficient Communication: Miscommunications between the project team members and

managerial participants can lead to difficulties with non-compliance of rules and regulations. .

 Employees' skills and systems maintenance:

Success Factors:

Training and Skill Expertise: Giving employees the opportunity of getting training ensures that
they possess the skills necessary for the maintenance and operation of the system.
19 | P a g e

Archiving and Record-keeping: Maintaining systems with meticulous documentation

facilitates transmission of data and ongoing maintenance.

Sustained Development and Advancement: Creating a Setting where Workers Are Constantly
Gaining Knowledge and Skills.
Failure Factors:

Lack of Training: If the employees have not gotten proper instruction, they may find it difficult
to use the recently introduced framework effectively.

Insufficient Documentation: When an infrastructure has insufficient or missing records, it can

be challenging for staff to maintain the development and troubleshoot the problem.

Staff Resistance to Change: Employers may find it more challenging to effectively bring about
and sustain changes if personnel are resistant to adopting new practices or technological
innovations.

 Change Management and User Involvement in the Development Process:

Success Factors:

Operative Change Management: Beneficial change management allows for a planned strategy
for managing change that involves stakeholders, clarifies advantages, and addresses problems.

User Involvement: Two ways that end users actively participate in the IT framework developing
process are through participative feedback sessions and user experience evaluations.

Transparency of data: Good user participation is facilitated by clear communication about the
objectives, benefits, and drawbacks of the system that was created.

Failure Factors:

User’s Rigidity: Resistance to Change: Reduced system implementation and insufficient

acceptance may arise from users' aversion to change if it is not addressed.

Insufficient User Involvement: The system might not fully satisfy users' needs if they are not
given enough credit and involvement during the design phase.
20 | P a g e

Inadequate Communication: Inadequate or unclear communication about the changes that have
been implemented can make clients angry and confused.

Conclusion:

The effective assessment and management of these elements is necessary for the new Pass IT
Driving School system to be implemented successfully. A project's overall effectiveness can be
positively impacted by the efficient management of critical areas like risk reduction, timely
fulfillment and budget compliance, staff availability, and active customer participation in the
planning phase.

Task 2:

An evaluation explaining how your design meets the user requirements identified and
identifying possible improvements and further developments.

Evaluation of the Pass IT Driving School System's Design in Relation to User

Requirements:

1. Swift interfaces run by Users:

Strength: The report and data entry forms, among other suggested user interfaces included in the
aforementioned design, are intended to be easy to use and intuitive. This meets the requirements
that users have for an easy-to-use system.

Improvement: Regular usability testing with prospective customers may provide valuable
insights into areas that are still unclear or less intuitive. Constant improvement based on user
feedback guarantees the best possible experience for users.
21 | P a g e

2. Precise and Accurate Reporting:

Strength: Weekly schedules and progress for learners reports, among other detailed
documentation, are satisfied by the report formats. They provide relevant information in an
organised manner.

Improvement: Regular feedback sessions with instructors and leadership can identify additional
reporting metrics or visualisation features that could enhance observing and decision-making.

3. Ample Approach for Booking Lessons:

Strength: The flow chart and data flow diagrams provide a thorough and logical process for
scheduling lessons, meeting the user's need for a well-organized way to do so.

Improvement: Regular feedback from driving instructors and office staff can help identify any
barriers or shortcomings in the reservation process. Iterative improvements should lead to even
more streamlining of the process.

4. Steadfast and Manageable System:

Strength: By taking privacy concerns and cross-device interoperability into account, the
suggested solution satisfies user demands for a safe and simple to operate system.

Improvement: To keep ahead of possible threats, conventional audits of safety and upgrades
should be carried out. Accessibility audits have the ability to identify parts that users with a
variety of needs may need to have improved.

Possible Improvements and Further Developments:

i. Collaboration with Mobile Apps:

Develop specialized mobile apps to improve the availability and make the course management
easier for teachers and students who are always on the go. This is consistent with the growing
trend of using mobile devices.

ii. Automation of Notifications:

22 | P a g e

Provide instructors and students with automatic notices about upcoming sessions, schedule
modifications, or other essential details. This improves communication and reduces the
possibility of data being overlooked.

iii. Incorporation of a GPS System:

Provide GPS integration so that you can follow the teacher's and the class's activities in real time.
This tool could be used to check how well lessons are being taught and to remind people to
follow safety protocols.

iv. Online Learning Platform:

Concerning the creation of a web-based educational site that provides extra study tools and
resources to aid in concepts exam preparation. This might raise the bar for the services that
the driving school provides.

v. Feedback System:

Provide a methodical feedback system so that teachers and students can receive feedback on a
continuous basis. Utilizing brief feedback forms or post-lesson questionnaires can help improve
the overall standard of the facilities offered.

vi. Upgraded Data Analytics:

Use advanced data analytics features to provide insights into trends, student performance, and
the efficiency of instruction. Making strategic choices and maximizing the operations of
the driving school may derive advantages from this.

Conclusion:

The Pass IT Driving School system is made to accommodate the needs of its users and provides
a solid framework for efficient lesson planning, managing time, progress tracking, and report
submission. Iterative advancements, regular feedback from consumers, and usability evaluation
are necessary to keep the system up to date with evolving user needs. The planned innovations
23 | P a g e

and updates are meant to enhance not only the system's user interface's visual appeal as well as
effectiveness but also its overall practicality for both instructors and students.
24 | P a g e

References

Aulika Chakravorty,A. Samyadip Chakraborty, S. Jigeesh, N. (2019) Analysis of Agile

Testing Attributes for Faster Time to Market: Context of Manufacturing Sector Related IT
Projects, Procedia Economics and Finance: Volume 11, pp. 536-552.

Broad, J. (2013) ‘Chapter 5 - System Development Life Cycle (SDLC)’, in J. Broad (ed.)
Risk Management Framework. Boston: Syngress, pp. 39–45.

Danette McGilvray, (2021) ‘Chapter 5 - Structuring Your Project, Executing Data Quality
Projects (Second Edition), Academic Press: 2021, pp. 253-267.

Govil, N, Sharma, A. (2022) Validation of agile methodology as ideal software development

process using Fuzzy-TOPSIS method, Advances in Engineering Software, Volume 168.

Rafael Parizi, R. Prestes, M. Marczak, S. Conte, T. (2022) How has design thinking being
used and integrated into software development activities? A systematic mapping, Journal of
Systems and Software, Volume 187.