0% found this document useful (0 votes)
66 views1 page

Assignment #3 - UID

This document provides instructions for Assignment #3 on user interface design for a systems analysis and design course. Students are asked to develop a mockup of the user interface for their proposed system using software like PowerPoint or Moqups. The mockup should include each necessary screen and allow reviewers to navigate between screens. Students must also provide a written submission answering questions about design considerations, inputs and outputs for each screen in their mockup. The goal is to reduce ambiguity in the system design before implementation.

Uploaded by

Comicleaks 1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
66 views1 page

Assignment #3 - UID

This document provides instructions for Assignment #3 on user interface design for a systems analysis and design course. Students are asked to develop a mockup of the user interface for their proposed system using software like PowerPoint or Moqups. The mockup should include each necessary screen and allow reviewers to navigate between screens. Students must also provide a written submission answering questions about design considerations, inputs and outputs for each screen in their mockup. The goal is to reduce ambiguity in the system design before implementation.

Uploaded by

Comicleaks 1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

CIS 375: Systems Analysis and Design

Assignment #3: User Interface Design


50 Points
Purpose: The following assignment serves to reinforce the content found in Module 8 of your textbook.
Our goal as Systems Analysts is to maximize both the efficiency and effectiveness of the business by
bringing technology solutions to the table in order to best use our organizations resources.

As part of that mission we want to ensure that when taking on a project there is little to no ambiguity
before we begin writing code and implementing our solution. We reduce this ambiguity via the first
three steps of the SDLC by:
- Understanding the business context and value proposition of our systems request in the
Investigation phase
- Understanding process and functional requirements during the Analysis phase
- Developing a blue print for execution as part of the Design phase.
In this assignment you will be developing a UI (User Interface) for your systems request.

Instructions: This submission will have two separate deliverables, this will represent the first initial
draft of your user interface.
1. Mockup (30 points) – Develop a mockup using any tool you deem fit (e.x. PowerPoint,
Moqups.com, Adobe XD, Marvel.com, etc) to develop a complete end-to-end mockup of your
application. For clarity, your mockup should include:
a. Each screen necessary for the system you have described in your use cases, user
requirements, etc.
b. The ability for a customer/reviewer to be handed your mockup and understand how
each screen is/can be related (i.e. something that can be navigated by clicking the
relevant UI elements to be brought to the related screen).
Note: Most mockup tools provide an mechanism to “export” your mockup, this should
provide a link to your mockup which can be shared with me as part of your submission.
2. Written Submission (20 points)– Develop a written submission for each frame/screen on your
mockup. For each please answer the following 3 questions:
a. Tell me what considerations you made with respect to overall design of the screen.
b. Describe each screen (contained within your application) and/or external entity (i.e.
other system) which represents an input into this screen.
i. Note: A flow chart depicting screen to screen can also be used for illustrative
purposes if you find this easier.
c. Describe the screens (contained within your application) and/or external entity (i.e.
report, dashboard, other system) that this screen
i. Note: A flow chart depicting screen to screen can also be used for illustrative
purposes if you find this easier.

You might also like