BSc (Hons)/FdSc Computer Science
Systems Analysis and Design
Table of Contents
Task 1: Assessing SDLC Models 2
Task 2: Information Gathering with Interviews and Surveys 3
Task 3: Detailed Design Documentation 4
Task 4: User Interface Design 5
Task 1: Factors Affecting the Success and Failure of the New System 5
Task 2: Evaluation of Design and Future Improvements 7
Part A
Task 1: Assessing SDLC Models
Two SDLC models will thus be assessed for their suitability concerning parameters such as the expected size of the project, the degree of technical complexity, and the ability to accommodate potential changes while building the driving school system effectively. The Waterfall Model consists of a strict linear spanning process in which one stage must be completed before a move takes place to the next stage; therefore, it is suitable for smaller projects, which have a clear requirement. Advantages include transparency in planning and easy manageability. The main disadvantage of the model is that for larger or more complex projects, the requirements might change once the development has started, and further activities in this mainline might lead to prohibitive costs. Other than that, the Agile Model provides interactivity that accounts for the changing requirements through ongoing collaboration with the different stakeholders. It must be remembered that this ease of access as regards flexibility and adaptability is good for developing projects where the said requirements are either prone to changes or are not fully known at the start (Franch et al., 2023). Quite on the other side, Agile requires active customer involvement during the entire development process to manage scope well and avoid issues such as scope creep.
The Waterfall Model
The Waterfall Model comprises the traditional processes of SDLC, with linear and sequential characters. The model is subdivided into phases such as requirements gathering, system design, implementation, testing, deployment, and maintenance. Each phase ends before the starting of another phase, with very little recourse to return to or modify earlier phases once completed.
One of the biggest advantages of the Waterfall Model is clarity and simplicity (Thesing et al., 2021). Each phase has clearly defined goals and deliverables; this makes it simple to follow development and the project manager’s tasks to check if everything has been done. Generally, this structured approach works well for smaller projects or those that have clearly defined requirements and are not likely to change. For example, suppose IT Driving School defines all its features and functionalities, such as booking a lesson, student record management, and scheduling tests; then the Waterfall Model will help in assuring systematic compliance with these requirements.
Another area where the Waterfall Model excels is in its insistence on documentation. At every stage of development, highly detailed documentation is prepared that serves as a reference point for stakeholders and also developers. This is especially relevant for the driving school system since this helps the development team to keep a very clear record of requirements, design specifications, and test results. The documentation helps ensure continuity even when team changeovers happen during the project. On the other hand, the Waterfall Model is also associated with certain disadvantages. The most significant disadvantage is that it is inflexible (Gumiński et al., 2023). When a phase is completed, it is difficult and expensive to return and make changes.
The Agile Model
Agile is an iterative and flexible model for software development. The Waterfall Model is not linear and unlike this. Here, the product development process is through small iterations or sprints, where each iteration is expected to deliver a functional element of the overall system (Iderima, 2023). Thus, stakeholders engage throughout the development process and provide continuous insight for possible changes to be made as per the growth of the project. Flexibility is one strength of the Agile Model. Being workable to changing requirements makes it well-fitted for projects where the exact scope may not be very well understood from the beginning. The Pass IT Driving School system could also take the initial functionality development in modules, such as lesson booking and managing student records, to build on other features like automatic test scheduling or progress analytics continuously with users’ changing requirements.
The Agile Model puts a high premium on collaboration between developers and stakeholders. It therefore follows that regular meetings or stand-ups would keep everyone on the same page, and possible issues can be majorly resolved the moment they crop up. With this well-coordinated effort, a significant possibility arises that the resultant product may qualify to meet user needs and expectations (Lelo and Israel, 2024). For instance, about Pass IT Driving School, there would also be input from instructors, office staff, and even students, while the specific requirements would be ensured. One of the advantages of Agile is that early and continued testing is emphasized. This allows developers to pull together various testing efforts, which can help detect and fix problems at any time during software development. Through this, as most major problems are easily resolved, less time is wasted and fewer resources are consumed.
Task 2: Information Gathering with Interviews and Surveys
Interviews will also be conducted to map the stakeholder’s needs completely. The interviewees will include instructors, office staff, and students. The conduct of the interviews will revolve around finding out the pain points for each of them under the old system, finding out what would be expected of the new system to improve the old system, and finding out what would be in a new system for each stakeholder. For instance, the instructors could be expected to field questions about their current issues on lesson scheduling and tracking student progress while the office staff could talk freely about administration tasks and data management necessities. Questionnaires will also be constructed to ascertain and validate a larger audience with implementation issues concerning the new system. Surveys will focus on investigating ways the system can improve efficiency, the user experience, and overall effectiveness in managing driving lessons and student records (Nousopoulou et al., 2022).
Surveys extend interviews instead of using opinions from a single audience. A good survey collects opinions on possible features, user interface desires, and improvements to the system. For example, students might be asked about their preferred methods for booking a lesson or receiving progress updates. This work would inform how to create a user-centered booking process. Surveys provide the additional benefit of finding ongoing problems or cross-verifying what has been stated in interviews (Schippers, 2024). This twofold strategy collects qualitative and quantitative data, thereby anticipating a problem that needs addressing, as well as a problem that has to be resolved.
Task 3: Detailed Design Documentation
Full-fledge details of design documentation for the Driving School System will comprise complete data flows at all standard levels such as context/0-level, level 1, and level 2 to publicly convey the flow of information in the system. These key processes include booking a lesson, student records, testing times, and assigning an instructor. In addition to the data flow diagrams, flow charts will be used to depict and detail each of the processes, including the decision points, inputs, and outputs for system operations and functionality (Seifermann et al., 2022).
Detailed design documentation Pass IT driving school system targets the clear and structured representation of data flow and other processes of the system. Data flow diagrams describe how information moves through the system stepwise. The context-level diagram will show that the system functions as a process with some external entities comprised of students, instructors, and the school office. The process will subsequently be broken down in the Level 1 DFD into sub-processes such as booking lessons, managing payments, and scheduling tests. The Level 2 DFD will break this down further for detailed DFD representation of such sub-processes as input fields for the student’s booking request or the workflow for updating lesson progress (AHISHAKIYE, 2024). In addition to the DFDs, flowcharts for each of these will also be created to show the sequence of actions in such significant operations as booking a lesson or processing a payment. All these will contain decision points, inputs, and outputs for identifying logical workflows.
Task 4: User Interface Design
Classy modern designs are meant the user interface of driving school systems for the data entry forms. These will have structured formats for specified fields starting from students’ details, lesson schedules, instructor allocations, and even payment records. The methods of data entry shall keep in mind easy to use as well as highly accurate measures necessary for efficient capture and management of data. Hardware and software requirements will also be provided for use in the day-to-day operations of the system while considering scaling up and integrating with the existing IT infrastructure (Khan et al., 2023). This design approach will help to improve usability while making operations more efficient for staff and instructors at Pass IT Driving School.
The UI design that will be involved in the development of the Pass IT Driving School system will always be a design that focuses on simplicity and usability. Each screen layout will have a clear layout and easily understandable navigation so that users can use their time accessing and managing information more easily (Alarcón et al., 2022). As an illustration, the data entry fields on the student registration form will include the following fields: name, contact detail, lesson type, and preferred instructor. Possible methods of data entry may include drop-down menus, radio buttons, and calendar pickers, and will help simplify the data input such that not much chance for errors exist. It will also show the instructor and staff dashboard features that show the schedules, upcoming lessons, and their payment statuses at a glance. The design will work well if accessed from any mobile device enabling users to easily access the system using smartphones or tablets.
Part B
Task 1: Factors Affecting the Success and Failure of the New System
Timeliness and Budget
Most importantly, completing the project on time and to budget affects a project adversely if there are delays. Operationally, a school can be highly disrupted by these delays, leading to huge stakeholder frustration, and therefore the project generally costs more as a result. Strong project management ensures that anything gets accomplished on time as agreed to. Once again, appropriate measures are put in place for budget constraints. Effective allocation of resources and prioritization of significant features make it possible to avoid overspending (Ahsun and Elly, 2024).
Organizational Policies
One more critical factor is compliance with the accepted policies and procedures of the driving school. The system must meet the current workflows related to booking lessons, progress tracking for students, and administration of tests. Where a policy conflicts with these processes, there would be a tendency for staff resistance to the system because it makes it difficult for them to use it.
Staff Skills and Training
The staff who would use the system should have sound skills and technical capabilities because the fate of the system would lie on them. In the case of being unused to using the system or lacking requisite technical skills, their actions can lead to errors as well as inefficiencies and thus to reluctance in adopting the system. Elaborate training programs have to be in place and available for employees to become familiarized with the system and to promote confidence in its use (Ugbebor et al., 2024).
Change Control
Implementing a new system will call for the appropriate change management strategies. Resistance to change is a historical fact especially when the affected stakeholders receive little manual processes. To avoid such, participation in field development processes should be extended to staff and instructors so that they can own the system and hence reduce resistance. Periodically communicate to them the benefits and improvement of the work processes through the system to promote acceptance of the use of the new system.
User Involvement and Feedback
The user involvement in developing the system is going to determine the success of the system. Interventions such as teacher feedback, student feedback, and office staff feedback during development would help build a system that meets an appropriate measure of needs for all its users. The absence of user involvement in the design of any new product can send the product in dire straits failing to develop a tool addressing the true source of pain and hence garnering dissatisfaction in use. The Pass IT Driving School will be positively or negatively affected depending on the completion schedule, budget, organization policies, and personnel skills (Nousopoulou et al., 2022). In summary, because new systems depend on effective project management, the appropriate alignment of organizational policies, capacity building in training, proactive management of change, and continued involvement of users, Pass IT Driving School will be in the best position to achieve smooth implementation and desired results from the system at that time.
Task 2: Evaluation of Design and Future Improvements
The system is very much aligned with the client requirements collated in the information phase for Pass IT Driving School. Features such as lesson booking, progress tracking, and instructor scheduling were had to address the operational issues of the school, whereas these are made with user-friendly interfaces for easy navigation by the user category, whether instructor, office staff, or student. Online and database searching options and reporting menus are also valuable for making data easier to retrieve and manage in operations.
Scalability is considered one of the major strengths of the system. Future iterations can include additional services such as the automated processing of payments and real-time notifications for lesson updates (Johnson et al., 2024). Another improvement area that can be targeted is developing a mobile app to accompany the web system, thus allowing easy access to the system via smartphones. Regular updates and maintenance will ensure that the system runs correctly according to the evolving user needs. Feedback mechanisms such as surveys or suggestion forms can also be put in place to capture change requirements. This is how the system will evolve with the working of the driving school to maintain a better future in success and satisfaction.
The computerized systems’ design for Pass IT Driving School aligns with the major requirements identified from the preliminary gathering of information of the user for the system (Rao, 2024). The functionalities of the computerized system include the following: booking, progress tracking, instructor scheduling, and report generation, among other school operation requirements. Interfaces ensuring user-friendliness and easy layouts ensure the systems, as it is for students, instructors, and office staff identities, without extensive learning curves and errors. Quick access to information will further enhance the overall management and decision-making processes with the reporting menus and searching options.
The system is scalable and adaptable in design. Some things can subsequently be added to the system to enhance it, like automatic payment processing for lessons, real-time notifications on bookings for lessons, and integrations with third-party tools like calendars or communications applications. Armed with these features, the system’s functionality and workability for its end-users can only get better. Future improvement requires the development of mobile compatibility (Kashyap, 2024). A mobile app would enable the instructor, students, and staff to access the system anytime to arrange lessons and update progress and schedule for easy access.
References
AHISHAKIYE, M., 2024. ONLINE EQUIVALENCE APPLICATION MANAGEMENT SYSYTEM Case study: ONECS (Chad) (Doctoral dissertation, ULK).
Ahsun, A. and Elly, B., 2024. Optimizing Resource Allocation for Enhanced Project Efficiency.
Alarcón, J., Balcázar, I., Collazos, C.A., Luna, H. and Moreira, F., 2022. User interface design patterns for infotainment systems based on driver distraction: A Colombian case study. Sustainability, 14(13), p.8186.
Franch, X., Palomares, C., Quer, C., Chatzipetrou, P. and Gorschek, T., 2023. The state-of-practice in requirements specification: an extended interview study at 12 companies. Requirements Engineering, 28(3), pp.377-409.
Gumiński, A., Dohn, K. and Oloyede, E., 2023. Advantages and disadvantages of traditional and agile methods in software development projects–case study. Zeszyty Naukowe. Organizacja i Zarządzanie/Politechnika Śląska, (188 Nowoczesność przemysłu i usług= Modernity of industry and services), pp.191-206.
Iderima, E.C., 2023. The Impact Of Software Engineering On The Systematic Design And Development Of Instructional Systems.
Johnson, E., Seyi-Lande, O.B., Adeleke, G.S., Amajuoyi, C.P. and Simpson, B.D., 2024. Developing scalable data solutions for small and medium enterprises: Challenges and best practices. International Journal of Management & Entrepreneurship Research, 6(6), pp.1910-1935.
Kashyap, A.N., 2024. Development of Firmware for Control and Feedback System in an Upper-Body Exoskeleton (Doctoral dissertation, CALIFORNIA STATE UNIVERSITY, NORTHRIDGE).
Khan, K.A., Quamar, M.M., Al-Qahtani, F.H., Asif, M., Alqahtani, M. and Khalid, M., 2023. Smart grid infrastructure and renewable energy deployment: A conceptual review of Saudi Arabia. Energy Strategy Reviews, 50, p.101247.
Lelo, J.M. and Israel, B., 2024. Supply Chain Innovative Practices and Customer Satisfaction: Insights from Manufacturing SMEs. Management Dynamics in the Knowledge Economy, 12(1), pp.54-69.
Nousopoulou, E., Kamariotou, M. and Kitsios, F., 2022. Digital transformation strategy in post-COVID era: Innovation performance determinants and digital capabilities in driving schools. Information, 13(7), p.323.
Nousopoulou, E., Kamariotou, M. and Kitsios, F., 2022. Digital transformation strategy in post-COVID era: Innovation performance determinants and digital capabilities in driving schools. Information, 13(7), p.323.
Rao, W., 2024. Design and implementation of college students’ physical education teaching information management system by data mining technology. Heliyon, 10(16).
Schippers, D., 2024. Understanding the Value and Adoption of the International Patient Summary: Exploring Clinical Value, Facilitators, and Barriers (Master’s thesis, University of Twente).
Seifermann, S., Heinrich, R., Werle, D. and Reussner, R., 2022. Detecting violations of access control and information flow policies in data flow diagrams. Journal of Systems and Software, 184, p.111138.
Thesing, T., Feldmann, C. and Burchardt, M., 2021. Agile versus waterfall project management: decision model for selecting the appropriate approach to a project. Procedia Computer Science, 181, pp.746-756.
Ugbebor, F., Aina, O., Abass, M. and Kushanu, D., 2024. EMPLOYEE CYBERSECURITY AWARENESS TRAINING PROGRAMS CUSTOMIZED FOR SME CONTEXTS TO REDUCE HUMAN-ERROR RELATED SECURITY INCIDENTS. Journal of Knowledge Learning and Science Technology ISSN: 2959-6386 (online), 3(3), pp.382-409.