Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

CS1004 - Information Systems and Organisations > Block 2 > Flashcards

Block 2 Flashcards

(65 cards)

Start Studying
1
Q

What is the definition of Lifecycle?

A

**Lifecycle - The process of analysing designing and then implementing software**

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
1
Q

What are the different stages in the software lifecycle

A
  1. System analysis - understanding and defining the system needs to do
  2. System Design - Describing in text, drawing and digraming how the system and its components should be
  3. Implementation - programming and developing the documentation
  4. Validation - Testing for bugs and wether ite meets the requirements
  5. Maintenance - Modifying and upgrading after installation and operation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the different methodologies of software development

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the different requirements of system dev?

A
  1. Functional requirements
    1. What systems must do
  2. Non-functional requirements
    1. How a system must do it
    2. Constraints and qualities of a system
    3. Include usability, performance, maintainability, security and legal constraints
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Identify which requirements are functional and non-funtional

A
  1. Functional
  2. Non-Functional
  3. Functional
  4. Non-Functional
  5. Non-Functional
  6. Functional
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the steps in system analysis?

A
  1. Gather Requirements
    • Look at business processes, activities and transactions
    • Look at documents
    • Look at existing systems
    • Look at the current market
  2. Analyse Requirements
  3. Specify Requirements
  4. Validate Requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What does an analyst do?

A
  • Understand and communicate with clients/users
  • To establish business / user needs
  • Strong technical backgrounds allowing for technical requirements to be made
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Explain this graph

A

****Requirements is the most crucial part that allows for better and easier developments****

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is a statement scope?

A
  • Agree on scope of the system
    • High level overview of deliverables
  • Agree on what will not be in the system
  • Agreements to protect the developers to avoid external requests
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is ATOMs statment scope?

A

The function of the ATOM sales order system is to manage the transaction process between a customer placing an order through final payment. WILL NOT include stock management function

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are use Cases?

A
  • Describes interactions between a user to see a goal
  • User will interact, system will respond
  • In a swquence of steps
    • What the user does
    • What the system should do in response
      • The FUNCTIONAL REQUIREMENTS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are the different components on use cases?

A
  • Primary Actor - Customer
  • Goal - Aim of funtion
  • Scope - Use cases
  • Main Sequence - Interactions between systems and user
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the different use case types?

A

Interactions with software - Business use case

Actor to the business itself (description of a system that automates a process)

Buisness organisation + processes - System use case

**Actor to internal system**

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are use Cases?

A
  • A goal
  • Used in requirements and analysis stage of system dev lifecycle
  • Describes user / stakeholder (primary actor) system interactions
    • To achieve a goal
  • Describes the sequence of steps and system behaviour during interactions
    • Can includes supporting actors which can be systems
      • When external support required
    • Which will have their own goals that need to be met too
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

How do you layout use cases?

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Make a goal list for an ATM transaction

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is a business use case?

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What is a system use case?

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q
A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What is the different levels of use case detail?

A
  • Basic (Casual) use case
  • Detailed (Fully dressed) use case
  • The further a project processes, the more detailed use cases are needed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

What is a general use case?

A

Contains

  • Primary Actor
  • Goal
  • Scope/goal
  • Main Success Sequence
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

What is a fully dresses use case?

A

Contains base use cases

  • Primary Actor
  • Goal
  • Scope
  • Main Success Sequence

Contains Further detail as well

  • Supporting actors - Other employees + stakeholders
    • Stakeholder - something or someone with a vested interest in the behaviour or outcome of the use case
  • Triggers
  • Preconditions
  • Guarantees (Success + Minimum)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

What are ATOMs stakeholders and intrests?

A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

What are triggers?

A

Triggers

  • Event that initiates the use case
  • What causes the actor to start it
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
What are pre-conditions?
- What must be true before the use case can occur - Assumptions about the state of the world - Things that have happened already
25
What is the pre-conditions and triggers of ATOM?
26
What are guarentees?
27
What are extensions/exceptions?
- Events that can go differently or wrong - Forsights that should be taken into account during system design - So proper reposes are created - Like system prompts instead of crashing - Hardest part of use cases - Biggest contribution to require analysis - Added after main sequence in a use case template - Which includes guarantees too
28
What are the different extensions conditions that apply to ATOM?
28
How do you add an extension?
29
What are the extension handlers for these conditions in ATOM
30
What are guarantees?
- Outcomes of what must be true after use case occurrence - Success guarantee - Use case succeeds - main sequence → success guarantees - Minimum guarantee - Extensions → minimum guarantees
31
What are the components of a fully-dressed use case template?
32
What can UML diagrams be used for?
- Use cases can be represented as UML diagrams - Unified modelling langaguage - System Design Diagram Standard - Requires narratives to be used effectively
33
How does consistency and completness apply to analysis and design?
- Consistency + Completeness used to assess that analysis and design is fit for purpose - Consistency → Are entires in different parts of the use case consistent - Completeness → for any step is there another use case that provides relevant data
34
What are use case rules?
- Description of user behaviour and interaction with users - Communicating device between all stakeholders involved in system development - Detailed and complex as needed - NOT user interfaces - Functional requirements - Leads to success or known failure
35
What is system design?
- How a system should be made - Uses diagrams drawings and text To design: - Overall architecture - User databases - User interfaces - Programs
36
What is database design?
- Information system - Collections of programs and a data storage structure - Essential for data needs identification + data storage
37
What are entities?
- Type of thing that an org wants to hold data - Can be people like stend or lecturer or online platforms
38
What are attributes and the different types of attributes?
- Data we need to know and collect **Student_name, student_ID, Student_DOB** **********Simple Attributes********** - AKA atomic attributes *Student id* ****************************************Composite attributes**************************************** - Many parts *******Name = title + initial + surname******* **************Single-valued OR Multivalued attributes************** **********Derived attributes********** - Attributes taken from a process involving
39
What is an attribute domain?
Set possible values of an attributes ******************************The domain of the attribute month could be January, Febuary******************************
40
What are relationships?
- Two or more entities linked to one another - Lecture teaches module
41
How do you represent entities and relationships?
42
What is the entity relationship diagram
43
What is cardinality?
43
How do you represent cardinalities with a number?
44
How do keys and realtionships work with entity relationship diagrams?
primary keys - Attribute that uniquely identify an entity key - create relationships between entities 1→many relationships - Primary key form the one end is added as foreign key in the many end 1→1 - both ends may have the same primary keys
45
What is the relationship diagram for ATOM?
46
What is design?
- Database Design - Struct of the data - Explore what data needs to be stored and how - Entity, attributes and relationship identifications
47
What do ERD's not tell us?
- Shows static structure of data - Doesnt show changes in data - Events and states are required
48
Give an exmaple of events, states and entities?
49
What are events?
- Something that happens in the environment - Causes entities to transition from one state to another - Needs ********************either or both******************** response and recording
50
What are events
- Something that happens in the environment - Causes entities to transition from one state to another - Needs ********************either or both******************** response and recording
51
************************************************What are the events and response in a sales order for ATOM?************************************************
52
What are states?
- Recognisable period in the life of an object - Different states = - Different capabilities - Different constraints - Different characteristics - Object remains in a state until triggered by an event
53
What is the different notation for states and transitions?
54
What is a transitent state?
55
What is a guard/guarded transition?
56
What are state diagram?
- Represents different states in the life of a Data Entity - Could describe all aspects of the systems behaviour and its sequence of events - Computer programs - UI dialogues - Business process (Sales Order)
57
What the state diagram for this process?
58
What are activities?
- Ongoing process (state) of performing some action - Rep using activity diagrams - Shows ordering of activities and transitions between them - Shows concurrent activities, responsibilities and dataflows - Transitions are timeless
59
What are the uses of activity diagrams?
- Sequencing of a Business Use Case - Business work flows and responsibilities - Sequence of System Use Cases
60
What is UML notation?
61
What is advanced notation UML?
62
What is the UML diagram for this sequence for a buisness process?

CS1004 - Information Systems and Organisations (12 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions