CMIS 270: Exam 3

- create an interface that is easy to learn/use - enhance user productivity - provide feedback to user actions - create an attractive layout/design - enhance the interface - focus on data entry screens - covered in input/validation

screen design guidelines

- login - navigation - data input - report generation

purpose of screen design

screen design

are the areas of the system where users can enter, update, and/or delete data

report design

are views of the data formatted for a specific use

- create a unique site identity and strive for consistency - natural eye movement - white space - margins - zones

layout guideline

- default values - range control - picture control - null value control

data integrity control

default value

value a field assumes unless explicit value is entered

range control

allow limited set of permissible values

picture control

pattern of codes that restricts the width and possible values of each position in a field

null value control

Special value indicating that the value for a field is missing or unknown

- content - repetition - alignment - proximity

CRAP

content

should be meaningful

repetition

navigation

alignment

of text boxes and aligned to the business process

proximity

don't want users to move all around the screen to enter data, fields should be close to each other

data input

screens; putting data IN; used for inputting data to your database

data output

report; viewing/retrieving data FROM; used to retrieve data from your database

SDLC stage 1 deliverable

Process Identification and selection -List of projects to be undertaken

SDLC Stage 2 deliverable

Process Initialization & Planning -Scope Statement, Project Schedule plan

SDLC Stage 3 deliverable

Analysis -Description of Solution (not detailed)

SDLC Stage 4 deliverable

Logical Design -Samples of Screen shots, reports, websites to be created

SDLC Stage 5 deliverable

Physical Design -Data dictionary

SDLC Stage 6 deliverable

Implementation -User manuals, actual code, test plans, user documentation, system documentation

SDLC Stage 7 deliverable

Maintenance -Documentation of fixes and troubleshooting

Agile Step 1

Market: Talk to customers

Agile Step 2

Analysis: requirements, user stories

Agile Step 3

Prioritize: Product owner

Agile Step 4

Estimate and Plan: come up with a team of planners

Agile Step 5

DO: Create code: 8 days

Agile Step 6

Demo

Agile Step 7

Retrospective

- fixed costs - fixed time - fixed scope

in SDLC the triple constraints are

- fixed costs - fixed time - est. scope

in Agile the triple constraints are

-In SDLC, quality is affected by time, budget, and scope -In Agile, scope is affected by time, budget, and quality.

Between the triple constraints for SDLC model and the Agile Manifesto, which of the following statements is/are TRUE?

2-4 weeks

how long is a typical sprint?

less about a set way of doing things

Agile primary philosophy

SCRUM

business value/impact

In an agile environment, which of the following is used to prioritize tasks?

Maintaining consistent standards, allowing shortcuts, and accelerator keys

Enhancing user productivity is the rationale for

false

Agile project teams are responsible for prioritizing which user stories will be completed in each sprint

noun phrases

How are data flow lines labeled?

true

A data flow diagram is referred to as an I-P-O model because every process inside of an information system requires data input and data output

card, conversation, confirmation

In relationship to user stories, what are the 3 Cs?

logical design

Functional, business related specifications of all system elements including how the system will look to the end user is developed in which stage of the SDLC?

User ID and passwords

What is the most common technique for managing user access to information systems?