This is a project of the semester where I had to pretend to be apart of a team developing a driving application called DrivePass. I would in be incharge of creating graphs for the company as well as mainly communicating with stock holders.
Here is what is included in this folder:
System Design document. Is graphs and diagrams for drivepass.
This includes:
2 UML activity Diagram
1 UML sequence Diagram
1 UML Class Diagram
1 UML Case Diagram
A power point that's suppose to be low level for Product owners to see some graphs and be included in the creation process of DriverPass
Speaker notes are to help you give the presentation. It's a more detailed version of the speaker notes on the slides themselves.
Rubric
Competency In this project, you will demonstrate your mastery of the following competencies:
Create various system models through the application of appropriate tools Present and articulate technical concepts to nontechnical audiences Scenario You work for a small consulting company that designs systems for various clients. You are continuing to work on a system for DriverPass. Previously, you completed a business requirements document for your project lead that articulated DriverPass’s needs. You also made a suggestion regarding which approach—object or process—your company should take. Based on your excellent work thus far, your project lead would like you to continue designing the system for DriverPass. Your project lead ultimately decided on a blended approach that incorporates the best of object and process modeling. She has asked you to complete a system design document, which will include several UML diagrams and a description of the technical requirements for the DriverPass system. This design document will eventually be shared with the developers on your team who will implement your design.
Finally, your project lead has asked you to create a short presentation for the client based on your design. You will be asked to communicate different components of the system and how they meet DriverPass’s needs. Since this information will be presented to the client, you will need to avoid the use of technical jargon.
Review the assignment directions below and follow the steps needed to complete these deliverables for your project lead.
Note: You will not be creating all of the UML diagrams for the entire system, nor presenting the entire design to the client. In the industry, you would have help from coworkers and a longer time frame to complete all of the documentation. For the purposes of this project, things have been simplified.
Directions System Design Document You will complete a system design document based on the requirements you collected in Project One. In this document, you will complete your system design by creating proper UML diagrams and describing the system’s technical requirements.
Review the business requirements document that you completed for Project One. This will remind you of your client’s needs and your plan for the design. Tip: It would also help to review any feedback your instructor provided on Project One. In Module Six, you created a UML use case diagram for the DriverPass system. If you would like to make any adjustments to your diagram, please do so. Check to make sure that you included appropriate components and symbols and that your design meets the client’s requirements. In addition to the use case diagram, you will use the CASE tool Lucidchart to create UML activity, sequence, and class diagrams. Each diagram must include the appropriate components and symbols and meet the client’s requirements. Based on the use case diagram you created: Choose two use cases and create two UML activity diagrams, one for each use case. For one of the use cases you chose, create a UML sequence diagram. Finally, you must use Lucidchart to create a UML class diagram for your system. Your class diagram should include the different classes and attributes needed for your system design. You are not required to include methods, but you may if you wish. Include a copy of each UML diagram in your system design document. Use the template linked in the What to Submit section. Review the different functional and nonfunctional requirements you included in your business requirements document for Project One. Based on these, describe the technical requirements of your proposed system. The technical requirements should address the required hardware, software, tools, and infrastructure necessary for your system design. Client Presentation You will create a short PowerPoint presentation to your client, which includes a description of your system. Your team lead wants to see your ability to present your ideas and designs back to clients. She would like you to include speaker notes for each slide that include your explanation of the slide and how it meets the client’s needs. Since you are presenting to a client, your explanation should be simplified and targeted at a nontechnical audience.
Open the client presentation template, linked in the What to Submit section. Each slide includes a heading as well as a prompt for what to include on the slide. You will present information from both your business requirements document and system design document. You must complete the following slides: Title System Requirements Use Case Diagram Activity Diagram Security System Limitations NOTE: You may include additional slides if you would like to explain other aspects of your design. Write out your explanation in the speaker notes for each slide. Use the PowerPoint Speaker Notes Tutorial, located in the Supporting Materials section, to help you with this task. Remember that these speaker notes represent what would be the spoken part of your presentation. Since you are explaining your designs to the client, you must do the following: Explain how each component of your design meets the client’s needs. Use nontechnical language to communicate your ideas. Clearly articulate your designs with polished grammar and sufficient detail.
Questions (This is for a homework assignment you do not need to read this)
- Briefly summarize the DriverPass project. Who was the client? What type of system did they want you to design?
In this project I was tasked to work for a small consulting company that designs systems. My client was DriverPass an upcoming driving school who wanted to offer test, training, and appointments for their driving students. It was up to me to show this information in a presentable way for the client to understand it as well as the development team to use this information and design a system. After a long consulting section where I had to gather information from a client I then made multiple charts documenting the experience.
- What did you do particularly well?
Something I believe I did well was creating charts in simplistic ways for people who aren't tech-literate. Anyone on the development team or on the product owner side could look at the charts and make sense of most if not all of the information being portrayed.
- If you could choose one part of your work on these documents to revise, what would you pick? How would you improve it?
The one part I would select would be the presentation. With the rigidness of the assignment I had to use a template for creating the power point. This leads to the powerpoint looking very plain and I believe if I was able to rework it in my own way I could make it look a lot nicer with better graphs as well as more slides to just in general explain more.
- 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 was able to know the users needs by having a document of the initional informational gathering step. Going forward I think it's imporant that you have some form of documentation while gatherting information from a client. This allows you to ensure you adding everything the client wants in their program. The user's needs are extreamly imporant in the designing of this program as they are the customers for your company. Just like how if you have an allergy you would hope the chef doesn't use what your allergic too in the meal the same can be said about software development. When developing software it's imporant for you to only add what's needed and requested as adding to many features could lead to Product Owners feeling upset or unheard.
- How do you approach designing software? What techniques or strategies would you use in the future to analyze and design a system?
Personally when designing software I like to take the top down design. I like to get a bigger picture of everything needed and slowly break it down into more manageable chunks. Doing it this way allows for developers to know excactly what the end goal is and allows them the flexability to adapt and change my blueprint if they would like. For Instance:
I want to create a Feature in a game where Players can store items First we would need to create an inventory for the player Second we need to figure out how the player picks up objects. Third we need to figure out what the item convention will be named.