IT6X29 Revision

Question 1 of 26

1

Select from the dropdown lists to complete the text.

What Are Requirements?

( System, non system ) Requirements:
( analyse, Functional, parting ) requirements
( Non-functional, analyse, parting ) requirements

Explanation

Question 2 of 26

1

Fill the blank spaces to complete the text.

FURPS+ Requirements Acronym?

requirements
requirements
requirements
requirements
requirements
+ even more categories…

Explanation

Question 3 of 26

1

Information Gathering Techniques Choose 6 that apply.

Select one or more of the following:

Interviewing users and other stakeholders
Distributing and collecting questionnaires
Reviewing inputs, outputs, and documentation
Observing and documenting business procedures
Researching vendor solutions
Collecting active user comments and suggestions
Making a speech in public
System Diagnosis

Explanation

Question 4 of 26

1

choose 6 that apply
Reasons for Modeling

Select one or more of the following:

Communicating with a variety of users and stakeholders
Documenting what was done for future maintenance/enhancement
Learning from the modeling process
Reducing complexity by abstraction
Remembering all the details
Communicating with other development team members
Using Data to help team
Applying customer skills

Explanation

Question 5 of 26

1

Some Analysis and Design Models
Choose 8

Select one or more of the following:

Event List
Use Case Diagram
Use Case Description
Location Diagram
Class Diagram
Sequence Diagram
Communication Diagram
State Machine Diagram
Venn Diagram
Database Diagram

Explanation

Question 6 of 26

1

Documenting Workflows with Activity Diagrams

Workflow.

Select one of the following:

describes user (or system) activities, the person who does each activity, and the sequential flow of these activities
Useful for showing a graphical model of a workflow
A UML diagram
sequence of processing steps that completely handles one business transaction or customer request

Explanation

Question 7 of 26

1

Documenting Workflows with Activity Diagrams

Activity Diagram

Select one of the following:

sequence of processing steps that completely handles one business transaction or customer request
describes user (or system) activities, the person who does each activity, and the sequential flow of these activities
Useful for showing a graphical model of a workflow
A UML diagram

Explanation

Question 8 of 26

1

Fill the blank spaces to complete the text.

Use Cases
— an activity that the system , usually in response to a by a user
Use cases define functional requirements
Analysts decompose the system into a set of use cases (functional decomposition)
Two techniques for Identifying use cases
User goal technique
Event decomposition technique
Name each use case using Verb-Noun

Explanation

Question 9 of 26

1

Fill the blank spaces to complete the text.

Use Case Diagrams

Use case diagram— a model used to graphically show uses cases and their relationships to actors
Recall UML is , the standard for diagrams and terminology for developing information systems
Actor is the UML name for a end user
Automation boundary— the boundary between the computerized portion of the application and the users who operate the application

Explanation

Question 10 of 26

1

Fill the blank spaces to complete the text.

Use Cases and CRUD
CRUD technique –

A good cross-check against the existing set of use cases. Used in database context
Ensure that all classes have a complete “cover” of use cases
Not for primary identification of use cases

Explanation

Question 11 of 26

1

Three Layer Architecture

Drag an answer into the correct orange point.

View Layer

Domain Layer

Data Layer

Web/Application Server

Database Server

View Layer Logic

Domain Layer Logic

Data Layer Logic

Explanation

Question 12 of 26

1

Stakeholders of a comprehensive accounting system for public company

Drag an answer into the correct orange point.

Operational

Executive

Internal

External

Bookkeepers, Accountants

Internal Auditors

Operational Managers

Senior Managers, Board of Directors

Partner Organizations, customers

External Auditors

Investors, Regulators

Explanation

Question 13 of 26

1

Verifying use cases for Customer

Drag an answer into the correct orange point.

Customer

Create

Read/Report

Update

Delete

Create Customer Account

Look up Customer,Produce customer report

process account update customer account

update customer account to archive

Explanation

Question 14 of 26

1

DA and DBA Responsibilities

Drag an answer into the correct orange point.

Data Administrator

Database Administrator

Standard, Ownership, Quality

Secretary

Admin

Secratary

Performance, Recovery, Enviroment

Software, Data Entry

management

CEO

Data Server

Application server

Application domain Data

Explanation

Question 15 of 26

1

First Normal Form

A ❌ is in first ❌ form if ❌ field ❌ only one value.
Not ❌ ❌ in an ❌
Not ❌ number of ❌

Drag and drop to complete the text.

table

normal

every

contains

multiple

values

attribute

varying

columns

Explanation

Question 16 of 26

1

Second Normal Form
A table is in Second Normal Form if it is First ❌ Form and each ❌ ❌ is only ❌ ❌ on the entire primary key.
This ❌ only arises with tables that have ❌ ❌

Drag and drop to complete the text.

Normal

non-key

attribute

functionally

dependent

situation

multiple

attribute keys

Explanation

Question 17 of 26

1

Third Normal Form
A table is in Third Normal Form if it is in ❌ and NO ❌ (or set) is ❌ on any other non-key attribute (❌)
In other words, no ❌ among any ❌

Drag and drop to complete the text.

2NF

non-key attribute

functionally dependent

or set

FDs

non-key attributes

Explanation

Question 18 of 26

1

Steps of Object-Oriented Design
Three paths
Simple use case use CRC Cards
Medium use case use Communication Diagram
Complex use case use Sequence Diagram

Drag an answer into the correct orange point.

First-Cut Design class Diagram

CRC Cards

Communication Diagrams

Sequence Diagram

Final Design Class Diagram

Package Diagrams

Identity Classes

Determine Responsibilities

Identify Messages

Define Parameters

Finalize Navigation

Determine Dependency

Explanation

Question 19 of 26

1

Example of CRC Card

Drag an answer into the correct orange point.

Responsibilities

Class Name

Collaborating Classes

Attributes

Customer

Update name, Update address

sale payment

Account Numb, Customer Name, Mobile Numb

home phone, Status

Request purchase History, Process Sale,

Make Payment

Explanation

Question 20 of 26

1

Example of System Requirment

Drag an answer into the correct orange point.

Functional requirements

Non-functional requirements

Business uses, functions the users carry

Shown as use cases in Chapter 1

other system characteristics

Constraints and performance goals

Activity's System must perform

Explanation

Question 21 of 26

1

Activity Diagrams Symbols

Drag an answer into the correct orange point.

Swim lane Heading

Manager

Starting Activity (Pseudo)

Review Financials

Transition Arrow

Prepare Report

Activity

Ending Activity (Pseudo)

No

Yes

Another way to show Decision

Synchronization bar (Join)

Synchronization Bar( split)

Explanation

Question 22 of 26

1

Name Analyse and design models

Drag an answer into the correct orange point.

Event List

Class Diagram

Sequence Diagram

Communication Diagram

State Machine Diagram

user case diagram

user case description

Location Diagram

Explanation

Question 23 of 26

1

Metaphors of Human Computer Interaction

Drag an answer into the correct orange point.

Direct manipulation metaphor

Desktop Metaphor

Document Metaphor

Dialog Metaphor

Explanation

Question 24 of 26

1

Many to Many Relationship

Drag an answer into the correct orange point.

Student

Class

StudentIDPK

ClassIDPK

1

1.

0.*

0..*

StudentName, HomeAddress, Phone, Age

StudentID PK

ClassName, Course, Tutor, Credits

ClassID PK

Explanation

Question 25 of 26

1

User Case Diagram

Drag an answer into the correct orange point.

customer

management

send/receive points

transfer mountain bucks

stores sale representive

send messages

process account adjustment

customer service representative

browse messages

view mountainbucks

reply to friend linkup

request friend linkup

create update customer acc

Explanation

Question 26 of 26

1

Systems Analysis Activity

Drag an answer into the correct orange point.

Gather Detailed Information

Define Requirements

Prioritize Requirements

Develop User-Interface Dialogs

Evaluate Requirements with Users

	Created by Katarina Christie over 6 years ago

Revise IT6X29 Systems Analyse

IT6X29 Revision

Question 1 of 26

Select from the dropdown lists to complete the text.

What Are Requirements? System non system( System, non system ) Requirements: analyse Functional parting( analyse, Functional, parting ) requirements Non-functional analyse parting( Non-functional, analyse, parting ) requirements

Explanation

Question 2 of 26

Fill the blank spaces to complete the text.

FURPS+ Requirements Acronym? requirements requirements requirements requirements requirements + even more categories…

Explanation

Question 3 of 26

Information Gathering Techniques Choose 6 that apply.

Select one or more of the following:

Explanation

Question 4 of 26

choose 6 that apply Reasons for Modeling

Select one or more of the following:

Explanation

Question 5 of 26

Some Analysis and Design Models Choose 8

Select one or more of the following:

Explanation

Question 6 of 26

Documenting Workflows with Activity Diagrams Workflow.

Select one of the following:

Explanation

Question 7 of 26

Documenting Workflows with Activity Diagrams Activity Diagram

Select one of the following:

Explanation

Question 8 of 26

Fill the blank spaces to complete the text.

Explanation

Question 9 of 26

Fill the blank spaces to complete the text.

Explanation

Question 10 of 26

Fill the blank spaces to complete the text.

Use Cases and CRUD CRUD technique – A good cross-check against the existing set of use cases. Used in database context Ensure that all classes have a complete “cover” of use cases Not for primary identification of use cases

Explanation

Question 11 of 26

Three Layer Architecture

Drag an answer into the correct orange point.

Explanation

Question 12 of 26

Stakeholders of a comprehensive accounting system for public company

Drag an answer into the correct orange point.

Explanation

Question 13 of 26

Verifying use cases for Customer

Drag an answer into the correct orange point.

Explanation

Question 14 of 26

DA and DBA Responsibilities

Drag an answer into the correct orange point.

Explanation

Question 15 of 26

First Normal Form A ❌ is in first ❌ form if ❌ field ❌ only one value. Not ❌ ❌ in an ❌ Not ❌ number of ❌

Drag and drop to complete the text.

Explanation

Question 16 of 26

Second Normal Form A table is in Second Normal Form if it is First ❌ Form and each ❌ ❌ is only ❌ ❌ on the entire primary key. This ❌ only arises with tables that have ❌ ❌

Drag and drop to complete the text.

Explanation

Question 17 of 26

Third Normal Form A table is in Third Normal Form if it is in ❌ and NO ❌ (or set) is ❌ on any other non-key attribute (❌) In other words, no ❌ among any ❌

Drag and drop to complete the text.

Explanation

Question 18 of 26

Steps of Object-Oriented Design Three paths Simple use case use CRC Cards Medium use case use Communication Diagram Complex use case use Sequence Diagram

Drag an answer into the correct orange point.

Explanation

Question 19 of 26

Example of CRC Card

Drag an answer into the correct orange point.

Explanation

Question 20 of 26

Example of System Requirment

Drag an answer into the correct orange point.

Explanation

What Are Requirements?

( System, non system ) Requirements:
( analyse, Functional, parting ) requirements
( Non-functional, analyse, parting ) requirements

FURPS+ Requirements Acronym?

requirements
requirements
requirements
requirements
requirements
+ even more categories…

choose 6 that apply
Reasons for Modeling

Some Analysis and Design Models
Choose 8

Documenting Workflows with Activity Diagrams

Workflow.

Documenting Workflows with Activity Diagrams

Activity Diagram

Use Cases and CRUD
CRUD technique –

A good cross-check against the existing set of use cases. Used in database context
Ensure that all classes have a complete “cover” of use cases
Not for primary identification of use cases

First Normal Form

A ❌ is in first ❌ form if ❌ field ❌ only one value.
Not ❌ ❌ in an ❌
Not ❌ number of ❌

Second Normal Form
A table is in Second Normal Form if it is First ❌ Form and each ❌ ❌ is only ❌ ❌ on the entire primary key.
This ❌ only arises with tables that have ❌ ❌

Third Normal Form
A table is in Third Normal Form if it is in ❌ and NO ❌ (or set) is ❌ on any other non-key attribute (❌)
In other words, no ❌ among any ❌

Steps of Object-Oriented Design
Three paths
Simple use case use CRC Cards
Medium use case use Communication Diagram
Complex use case use Sequence Diagram