Illustrate system requirements

From Computer Science Wiki
Revision as of 11:03, 17 November 2020 by Mr. MacKenty (talk | contribs)
System Fundamentals[1]

Once you have understood and chosen a system, you must diagram how the system works. This works prevents problems in the future by ensuring you understand all inputs and outputs, AND how a system is organized.

A flowchart is a type of diagram that represents a workflow or process. A flowchart can also be defined as a diagrammatic representation of an algorithm, a step-by-step approach to solving a task.

The flowchart shows the steps as boxes of various kinds, and their order by connecting the boxes with arrows. This diagrammatic representation illustrates a solution model to a given problem. Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields.[2]

About system requirements[edit]

Once you have selected a system you should map how the system will interface with other systems in the organization, how data will flow into and out of the system (the inputs and outputs), and how the system is organized. We use the three techniques below to understand this. Please watch this video for a very basic introduction to flowcharts.

Method Example Definition
system flow charts click here for example System flowcharts are a way of displaying how data flows in a system and how decisions are made to control events.[3]
data flow diagrams click here for example A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modelling its process aspects. A DFD is often used as a preliminary step to create an overview of the system, which can later be elaborated. DFDs can also be used for the visualization of data processing (structured design).[4]. Diagrams representing how information is moving through the system together with identifying all relevant inputs and outputs to the system. [5]
structure chart click here for example A Structure Chart (SC) in software engineering and organizational theory, is a chart which shows the breakdown of a system to its lowest manageable levels[6]

Real-world practical advice[edit]

This step is especially important when you are working with many different interdependent systems.

Do you understand this material?[edit]

Please consider the following examples, and answer the questions:

Example 1[edit]

This is a simple example:

A small business wants to plan a new system. The new system is a computer kiosk inside the store which allows customers to sign up for a email newsletter. If a customer signs up for a newsletter inside the store, they will get a 10% discount on their first purchase at the store. The owner hopes this 10% discount will be an incentive for customers to sign up for the email newsletter. The business will then regularly email the customers special offers and savings. The business owner expects to benefit from this system by having increased sales. The customers expect to benefit from this system by having access to special offers, to save money, and to see what is new and trendy at their store.

Question 1: Construct a suitable representations to illustrate system requirements

Do you have an advanced understanding of this material?[edit]

Example 2[edit]

This is a complex example:

A school of 900 students wants to plan a new system. The school hopes the new system is a secure web-based application which manages attendance data. The school administrators want to carefully track attendance for the students so it can identify when students have been absent for a customizable threshold. For example, the school might set a threshold of 5 absences within 30 days, which then automatically notifies the student, parent, and teacher there is a problem with attendance. The threshold might be 3 times within 10 days, or something like that. The system should keep track of attendance and tardies. The system should have customizable attendance codes. For example, "abscence for school trip", "excused abscence", "medical abscence" are all allowed abscence codes.

School administrators expect to benefit by having data about attendance so they can support students and parents to be in school. School administrators also expect to benefit by giving parents and students information about attendance (so parents can support their children to be in school). Finally, school adinistrators expect to benefit by using attendance data to apply for government funding (as they can prove how many students were in class on a specific day).

Parents expect to benefit by knowing when their children are in school or miss school. This way parents can support their children to be in school. Being in school is a shared value that the school hopes the parents share.

Students expect to benefit by understanding how many days of school of they have missed. The school expects students to have a strong "ownership of learning" and manage their attendance.

Question 1: Construct a suitable representations to illustrate system requirements

Standards[edit]

  • Construct suitable representations to illustrate system requirements


References[edit]