While working in a team environment, we worked closely with a client, Sweet Karoline’s Cakes, to analyze her current system and design a new one for her, based on her current business model and process.
System Requirements and Trace Matrix
Below is a copy of the system requirements and a trace matrix for the applicable use cases.
Use Cases and Use Case Diagrams
Below you can find a copy of the use cases I create for Sweet Karoline’s Cakes. These use cases included adding, updating, and deleting applicable data. In addition to the use cases, applicable Use Case Diagrams were created to illustrate how a user would interact with the system
Below is a copy of sequence diagrams that were created to display the relationship between Karoline, the user, the class, and a database.
Attached below is a copy of my class diagrams for Sweet Karoline’s Cakes. The class diagrams represents the applicable attributes and method for each class.
For each of the use cases that could have an applicable prototype, one was created. Attached below is my prototypes for Sweet Karoline’s Cakes. These prototypes were created using Visual Studios.
Team Planning, Use of Gantt Chart
To assist our team in the planning the workload of the project, a Gantt chart was created to allow each member of the team to work on his or her applicable section and know when their deadline was. This each process to be completed in a timely manner, especially processes that are dependent upon other tasks.
Inception Phase Specification
The below attached document was a milestone in the creation of our system for Sweet Karoline’s Cakes. The Inception Phase Specification analyzed Karoline’s system request, which included the business’ needs and requirements. A vision document then followed outlining the positioning of Sweet Karolone’s Cakes to the environment and also analyzed Sweet Karoline’s Cakes stakeholders and users. A product overview was then created which included assumptions and dependencies. From there we designed features of the product, including web hosting, payment systems, etc. This was then costed out to provide a Net Present Value for Karoline to reference. Functional and non-function requirements were then created which then drove the applicable use cases. A system architecture was also created to show the relationships between the user, Karoline, the payment management system, the database, etc. We then completed a risk analysis based on each use case and finally created additional prototypes.
Entity Relationship Diagram and Data Dictionary
Below is a copy of the Entity Relationship Diagram, ERD, for Sweet Karoline’s Cakes. A data dictionary was also created to estimate the approximate data usage for Karoline, as well as show relations between applicable tables.
Physical Architecture Design
Below is a copy of the physical architecture design for Sweet Karoline’s Cakes.