Login

Title

Problem Statement & Entity Relationship Diagram

Course

Databases

Abstract

This is the first of many milestones associated with a 6 week project. You will refer back to the requirements and design developed in this assignment in future milestones to a) Implement the design, b) Analyze the design for privacy and security issues, c) Design the software system and d) Develop and test the information system. This assignment has the following learning outcomes: ●To learn how to draft the requirements of an information system project using a problem statement. ●To learn how to draft a problem statement using the Function- Form–Economy-Time Model (FFET) ●To learn how to design an Entity-Relationship diagram, given the requirements of an information system. ●To learn how to explain the requirements of an information system, in a model that enables a software engineer to understand the capabilities of the system. ●To learn how to design an information system and rationalize said design in a manner that enables a software engineer to implement the design in a relational database system. ●To learn how to apply the practice of information modeling in a situation similar to those seen in the industry. ●To learn how to work within a team to resolve conflicts and accommodate varied design choices This is a team assignment and is ideally done in a team of 3 or 4 students.

Author

Sriram Mohan

Genre

ER Diagram, Problem Statement, Requirements Specification

Assignment Duration

One Week

Communication Skill

Writing, Teaming

Technical Skill

Design,Requirements Specification, Normalization

Workplace Scenario

As a software engineer, you will often be required to design information systems based on a client’s requirements. It is your responsibility to understand the needs behind the information system and develop a feature set based on the needs. Once you have captured the feature set, you will often be responsible for designing an information system that has the ability to store the required data in an efficient manner without any duplication.

The ER diagram is an industry standard and provides a visual representation of the database design. The ER diagram is the focal point of communication with the client and should be easy to read, modify and capture all the constraints to be represented in the database.

A critical ability while working within a team is to develop an ability to manage conflicts, accommodate different design decisions, and manage conflicting client requirements. This milestone helps you learn and apply these abilities in a real life situation.

Team Size

3

Collection

Citation

Sriram Mohan, “Problem Statement & Entity Relationship Diagram,” Incorporating Communication Outcomes into the Computer Science Curriculum, accessed September 25, 2017, http://cs-comm.lib.muohio.edu/items/show/30.

License

Creative Commons License

File: 333RHIT-ProjectAssignmentFramework3.doc

Comments

Allowed tags: <p>, <a>, <em>, <strong>, <ul>, <ol>, <li>