CS1004 Information Systems & Organisations

0.0(0)
studied byStudied by 15 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/54

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

55 Terms

1
New cards

Requirement

something a system must do/ a quality a system must have

2
New cards

Functional vs Non-Functional Requirements

functional is WHAT a system must do

non-functional is HOW the system must perform it

3
New cards

Feasibility study considers:

is it needed, can it be done, within budget, resources and time?

4
New cards

Statement of scope

A short concise statement of the primary purpose of the primary purpose/ function/ role of the system being developed. It states what will be in the system and what won't.

5
New cards

What does a use case do?

A use case is used within the requirement analysis and describes how a primary actor interacts with the system to achieve a goal. It also describes the system's behaviour as it responds to a request from an actor.

'Who' does 'What' with the system to achieve 'Which goal'.

6
New cards

Primary actor

Primary actors are people, or at times even other systems, that initiate an interaction with the system.

7
New cards

Actor

A stakeholder who interacts with the system during the use case (doesn't start it off- that's primary actor).

8
New cards

Stakeholder

Someone with a vested interest in the behaviour/ outcome of the use case.

9
New cards

Goal

What the actor in a use case wants to achieve through interacting with the system.

10
New cards

Scope

The scope defines the boundaries of the system in terms of its requirements (what it must do) and what explicitly isn't required.

11
New cards

Main Sequence

The sequence of steps/ events that occur in a case where nothing goes wrong. The ideal set of events that take place in a successful outcome of achieving a goal.

12
New cards

What do use cases capture?

The functional requirements/ intended behaviour of a system.

13
New cards

What are the two levels of detail when it comes to use cases?

Casual: contains Primary actor, Goal, Scope, Main success sequence.

Fully-dressed: contains Supporting actors, Stakeholders, Trigger, Precondition, Guarantees.

14
New cards

Trigger

The event that initiates the use case. What causes the actor to start it.

15
New cards

Pre-conditions

What must be true before the use case can take place.

16
New cards

Guarantees

The outcome that must be true after the use case has occurred.

17
New cards

Difference between Success Guarantee and Minimum Guarantee?

Success Guarantee: the outcome after a successfully run-through use case.

Minimum Guarantee: however the use case must end if not as the main sequence.

18
New cards

The sequence for use case with extensions

Primary Actor

Goal

Scope

Stakeholders

Supporting actors

Trigger

Precondition

Main sequence

Extensions

Success Guarantees

Minimum Guarantees

19
New cards

Entity

Something which an organisation may wish to hold data such as 'Student', 'Module'...

20
New cards

Attribute

The data we need to know/ collect about each entity such as 'name', 'studentID', 'DOB'...

21
New cards

What are the 5 types of attributes?

Simple (atomic): e.g. item_number

Composite: e.g. name = title + initial + surname

Single-valued: e.g. quantity

Multi-valued: e.g. hobbies

Derived: e.g. wage FROM hours_worked * hourly_rate

22
New cards

Attribute domain

A set of all possible values for an attribute. Such as the domain for 'months' could be Jan, Feb, March...

23
New cards

Relationship

How two or more entities are linked to one another.

24
New cards

Cardinality

How many instances of an entity relate to each instance of another entity.

25
New cards

Primary Key

An attribute that uniquely identifies an entity.

26
New cards

Events cause entities to...

Change state

27
New cards

Event

Something that happens in the environment.

28
New cards

State

A recognisable period in life of an object.

29
New cards

What is the 8 step process of Information Systems Development?

1. Project Initiation

2. Feasibility study

3. System analysis

4. System design

5. Implementation

6. Validation

7. Deployment

8. Maintenance

30
New cards

What are the 3 constraints of information systems development?

1. Scope

2. Time

3. Cost/ resources

31
New cards

Methodology

A set of procedures, techniques, tools, notations and documentation that helps a team to plan, manage, control and evaluate Information Systems Projects.

32
New cards

Advantages of waterfall methodology

- Practical and easy to use

- Simple structured approach (even novices can follow)

- Emphasis on documentation which makes it clear what phase the team is on

- Traceability and management facilitated

- With detailed documentation a new team can pick up where it was left off.

33
New cards

Disadvantages of waterfall methodology

- Requirements are always subject to change, waterfall is not as flexible to take on these changes.

- Slow and rework may take a while

- Low Flexibility, flows in one direction, very difficult to go back to change something

- Distance from users, only communication at the start and end of the process

- Errors may only be identified at the very end when testing is done

-Detailed documentation takes a lot of time and resources which aren't useful for small projects

- More prone to delays

34
New cards

Agile concepts

- minimal documentation as focused on providing software fast

- focuses on customer collaboration

- flexible to change

- extensive use of tools to speed up development ( code generator, automated tests)

- fixed resources (and therefore fixed budgets)

- accepts uncertainty as software is being released through iterative development

- better for small/ medium software

- no power hierarchy

- experienced developers

35
New cards

Product Backlog

A prioritized list of user stories, showing both short- and long-term goals of a software development. Normally the initial backlog contains just enough to get the development team started. More user stories/ use cases added throughout the process.

36
New cards

User stories

Describes features from the POV of the user which highlight a piece of functionality of the software. The template they follows is "As a... I want... So that...".

37
New cards

In terms of Feature prioritising, what does MoSCoW stand for?

M- must have

S- Should have

C- Could have

W- Won't have

38
New cards

What are the 3 key roles in Scrum development?

Product Owner: Represents the client, develops product backlog.

Scrum Master: Team and process facilitator.

Development team: team of 5-9 people responsible for creation of software.

39
New cards

Sprint

A full development cycle (design, implementation, testing) focusing on a user story/stories with a fixed length in advance ~4 weeks.

At the end of each Sprint, we have a working software, referred to as a potentially shippable product.

40
New cards

Corporate stakeholders

Person/ group/ organisation/ system who affects or can be affected by an organisation's action. e.g. employees, suppliers, customers...

41
New cards

The stakeholder theory classifies stakeholders by 3 characteristics, which are?

Power: the extent stakeholders can impose their will onto the project.

Legitimacy: The extent to which their involvement is appropriate.

Urgency: The extent to which the stakeholder believes it is critical to act now on their claims.

42
New cards

What does the stakeholder theory help with?

Helps identify what stakeholders should be consulted or 'managed'.

43
New cards

Soft Systems methodology

Focuses on better understanding the business and attempts to find a solution to the 'problem' without a information system development.

44
New cards

Rich Pictures

A cartoon visualisation of a situation based on field research, interviews...

They depict stakeholders, relationships, processes and view points.

These are used to help detangle complex situations.

45
New cards

Root definition

A description of what the system does, how, and why using CATWOE.

46
New cards

What does CATWOE stand for?

Customers: who the system serves.

Actors: who carry out the activities.

Transformation Process: what the system does what inputs get converted to outputs.

World View: the 'bigger picture', what matters in the world.

Owner: who has the power to change/ create the system.

Environment: relevant environment factors.

47
New cards

Conceptual model

The network of processes/ activities that must be done to satisfy the root definition. Compare with current state to plan what needs to change to go from current state to the next.

48
New cards

Business Strategy

The plan/ direction of an organisation for long-term plans.

49
New cards

SWOT analysis

Used to assess and understand a strategy, project, investment, or business decision in terms of internal factors- Strengths and Weaknesses, and external factors- Opportunities and Threats.

50
New cards

PESTLE analysis

An analysis tool focusing on the eternal business environment of the company. Tracks external factors that can affect activities & position of the company. This analysis can be especially good for a business considering a new product.

51
New cards

What does PESTLE stand for?

Political, Economic, Social, Technological, Legal, Environmental

52
New cards

Business model

A plan that details how a company creates, delivers, and generates revenues. A business model may also attract investors.

53
New cards

List the types of business models

Franchise, Subscription, Freemium, Advertisement, Retailer, Manufacturer, Distributor, Leasing, Razor Blades, Crowdsourcing, Peer-to-peer/platform.

54
New cards

Value Proposition

What the product/ service offers to the customers.

55
New cards

What are the 2 components of Revenue Model?

The cost structure: All expenses the business uses to deliver value to customers.

The revenue streams: All revenue streams the business utilises.