Challenge:
Describe phases of System Development Life Cycle and other development methodologies. Identify the main functions of the Systems Analyst. Create a Preliminary Investigation Report including Problem Statement development, Feasibility Analysis, Cost Benefit Analysis. Understand work breakdown structures and critical path method using Gantt & PERT Charts. Create a System Requirement Document including Requirement Analysis and Logical Models using context diagrams, data flow diagrams and object-oriented analysis to describe an information system. Create a System Design Specification including system interface, test plan and implementation plan. Design a system interface using the rules for successful interface design. Describe the elements of systems implementation including quality assurance, testing, training, and documentation. Work in teams to create the capstone project, maintain an individual journal describing step-by-step progress.
Solution:
We created a 53 page project in ten weeks. That went from an System Design Specifications through Functional Requirements, User Stories, Function Decomposition Diagram, Context Diagram, Data Flow Diagram Level 1, Data Dictionary, Entity Relationship Diagram, Class Diagram ,Object Attributes and Methods Object Relationship Diagram, Use Cases Sequence Diagram, State Transition Diagram, Activity Diagram, User Interface, User Documentation, as well as going through the System Environment, Implementation Requirements, and the Cost & Time estimates as well. This was a very challenging class but in truth one of the most rewarding experiences in my college career.
In my college experience (which was during the height of covid at the time) working from home and going to class with masks, we were put into three person teams. We never met in person everything was through discord, email, and google docs and this was an amazing experience most of these charts i’ve never heard of. As well as not knowing there functions either. Every week we would get the new class slides and learn, then discuss as a team what we would like to bring to this project. It was very rewarding our professor praised us quite a bit. At first I wasn’t comfortable and a bit overwhelmed but as we got into it I became more and more confident and was excited to show what I got in the group.
Executive Summary
Overview of the System:
Class Diagram:
Function Decomposition Diagram:
Wireframe
This was our original concept but it felt a bit bloated and felt unnecessary spaces.
User Interface:
This is what we settled on something simple that is familiar to the user.
Testing Plan
We included a training plan that will help users understand the processes of new MA software.
We really wanted to make sure that users would learn the system procedures within two days.