CS255

System Analysis and Design Course
• Briefly summarize the DriverPass project. Who was the client? What type of system did they want you to design?
DriverPass is a system aimed at helping aspiring drivers to pass their drivers test by giving informing lessons regarding driving. Customers can choose a certain package and then can set up an appointment with an assigned driver.
• What did you do particularly well?
I felt like I did particularly well was designing the different types of diagrams. It seemed like a challenging but satisfying experience connecting the different components of the system.
• If you could choose one part of your work on these documents to revise, what would you pick? How would you improve it?
I would like to revise the purpose of the project. I believe I could have gone into more detail on the whole reason why they want to develop DriverPass.
• How did you interpret the user’s needs and implement them into your system design? Why is it so important to consider the user’s needs when designing?
I had made sure I highlighted the important needs of the user during the interview such as being able to access the system from anywhere or being able to have access to all the accounts just in case of having to remove a user from the system. It is important to consider the user’s needs when designing because they are the ones who are mainly using the system. It is going to cause frustration and people refuse to use the system if you do not consider their needs.
• How do you approach designing software? What techniques or strategies would you use in the future to analyze and design a system?
The approach I take when designing software is a very strategic approach that welcomes iterative development, to ensure flexibility with the system. Especially in today’s society that is constantly evolving at a rapid pace. I first would like to identify the different users and figure out how they may move through the system. Some techniques and strategies I would use in the future to analyze and design a system are to first start simple and then branch off into more complex processes instead of trying to implement everything at once.