Week 2

Question 1

Methodology

Answer 1

Includes techniques to tie together tools and models in design

Allows the break-down into smaller manageable steps

Identifies and defines everything that needs to be done

Identifies resources needed in each step (staff, roles, availability)

Identifies who will do each activity

Provides a basis for project planning

Question 2

Project Planning

Answer 2

Project phases and activities

Deliverables

Milestones

Question 3

Models

Answer 3

Used to represent, record, or communicate information

Represent different aspects of real world

Requires abstraction (not detailed)

Models are graphical

Models in information system -> input, output, processes, users, data, objects, interactions, locations

Question 4

Techniques

Answer 4

Set of guidelines to assist an analyst with completing tasks and activities

Step by step instructions to build models

how to gather information from users

Question 5

Tools

Answer 5

Software support to create models

artefacts used to aid the designer in modelling and carrying out their techniques

visual modelling applications
word processor

Question 6

Predictive Approach

Answer 6

Requirements and needs are well defined/ understood

Careful planning

Projects with heavy regulation (banking)

Low technical risk

Requires lots of testing

i.e. Waterfall model

Question 7

Adaptive

Answer 7

Requirements and needs are uncertain and may be defined after initial development

Adjustments made according to change

High technical risk

Question 8

Waterfall model

Answer 8

System requirement
Software requirement
Analysis
Design
Coding
Testing
Operation

Question 9

Characteristics of waterfall model

Answer 9

Most popular

Sequential

Each step is frozen before moving on to the next step

Clear requirements

Easier to implement

Less resources

It does not support changes

Testing done after coding is fully completed

Question 10

Project Initiation + Planning

Answer 10

A preliminary investigation of the problems, opportunities, constraints and available resources

(cost+benefit)

Define scope (key stakeholders)

Key deliverable (feasibility report)

Question 11

Analysis

Answer 11

Understand the problems and opportunities

Agree on acceptance criteria (signoff on the system specification)

Assess feasibility again

Question 12

Design

Answer 12

Generate number of design options, technical, scheduling, economic, operational constraints

Acquire hardware and software (but nowadays prefers vendor or cloud)

Design interfaces, databases, network requirements

Specify integration requirements and software requirements (programs)

Question 13

Implementation, Testing & Deployment

Answer 13

Build/modify databases and networks as required

Complete coding

Perform various testing

Prepare users for new system (documentation, acceptance testing, training)

Finalise system and technical documentation

Install and deploy the system

Question 14

Alpha testing

Answer 14

testing to identify performance issues and bugs

conducted by testers

Question 15

Beta Testing

Answer 15

testing by limited amount of real users

Question 16

Performance Testing

Answer 16

process used for testing the speed, response time, stability, reliability, scalability and resource usage of a software application under particular workload.

Question 17

Unit Testing

Answer 17

individual units or components of a software are tested. The purpose is to validate that each unit of the software code performs as expected.

Question 18

Integration Testing

Answer 18

where software modules are integrated logically and tested as a group. A typical software project consists of multiple software modules, coded by different programmers.

Question 19

Usability testing

Answer 19

user experience, ease of use of the system

Question 20

Support Phase

Answer 20

Hypercare support phase right after deployment

It includes activities to upgrade or maintain the system after it is installed

Question 21

Staging environment

Answer 21

Environment that replicates production environment

Question 22

Testing environment

Answer 22

Testing environment , tests individual units

Question 23

Adaptive SDLC Approaches

Answer 23

Iterative (able to change)

Project can be refined by adjusting plans and models as project progresses

Conduct post -mortem (for learning)

Question 24

Agile

Answer 24

Guidelines for information system development in an uncertain and rapidly changing environment

Question 25

Agile manifesto

Answer 25

Focuses on individuals vs process

working software vs documentation

Collaboration vs negotiation

Responding to change vs following a plan

Question 26

study scrum flashcards

Answer 26

study scrum flashcards

Question 27

eXtreme Programming (XP)

Answer 27

Focusses on best practices of software development

Communication -> open communication

Simplicity -> simplest method that it will work

Feedback -> constant and meaningful feedback

Courage -> to do the right thing i.e. throw away bad code

Respect -> team members should respect each other

Question 28

Rules of eXtreme Programming: User stories

Answer 28

Use cases but written by customers about what the system needs to do for them

Question 29

Rules of eXtreme Programming: CRC Cards

Answer 29

Class, responsibilities and collaboration

Question 30

Rules of eXtreme Programming: Spike

Answer 30

Simplest possible program to address only the problem at hand

Question 31

Rules of eXtreme Programming : System metaphor

Answer 31

Using terms understood by both developers and customers

Question 32

Rules of eXtreme Programming: Pair programming

Answer 32

Code created by two people sharing one computer, to increase software quality

Question 33

Rules of eXtreme Programming: Refactoring

Answer 33

Removing redundancy and unused functionality, complexity

Question 34

Rules of eXtreme Programming: Others

Answer 34

Test-driven development
Continuous integration
Customer involvement