Reference no: EM132244389

Purpose of Context Diagram:

Using Visio for the development of a context diagram, provide a diagram that will demonstrate how the system should work ideally in your mind.

Identify 5 actors that will either input data into the system or might pull data from the system.

Here are a few advantages you will gain by using a timeline

• You will be able to design and share with your team the functional/operational expectations for the system.

• You will identify require users input.

• You will be able to avoid missed system responses to users.

• You will identify in advance stakeholders and the impact of user errors.

• You will identify areas where security must be implemented into the system.

Goals:

The student will be able to upon completion of this laboratory exercise be able construct a context diagram.

Objectives:

Given the current project the student will develop a project context diagram of the 5 stake holders that would be required to interact with the proposed system by:

A. Using Microsoft Visio create an icon to represents the system.

B. Identify 5 actors that must interact with system, e.g. Security administrator.

C. Identifying a task that each of the actors must perform when using the system.

D. Define the inputs require of the system to carry out the task using labelled input arrows.

E. Demonstrate system responses using labelled output arrows.

Deliverables:

Microsoft Visio file based on the assigned project that demonstrates the above objectives.

Functional/Non-functional Requirements Document

Purpose of Context Diagram:

Using Microsoft Word for the development of a functional/Non-functional documents.

This document will provide a list of 10 functional requirements that the system must perform and 10 Non-functional qualities that will system demonstrate that make the user happy working with the system.

Here are a few advantages you will gain by using a Functional/Non-functional requirement document.

• You will be able to define expected functions that the system should routinely perform.

• You will be able to avoid missed system function required to handle inputted data.

• You will be able to avoid missed system function response need to provide feedback to the end user.

• You will identify in advance the system response to user errors.

• You will identify functional security must be implemented into the system.

• You will be able to define expected that user has the system performance.

• You will be able to avoid system functions which will encourage the end use to use the system.

• You will be able to avoid designing system that will frustrate the end user.

• You will identify in advance how user expectation defines the system responses/responsiveness to  user errors.

• You will desired security by stakeholders and users.

Goals:

The student will be able to upon completion of this laboratory exercise be able construct a context  diagram.

Objectives: Given the current project the student will develop a Functional/Non-functional Requirement Document with 10 items listed under each heading using Microsoft Word.

Deliverables: Microsoft Word file based on the assigned project that demonstrates the above objectives.