Software Engineering - Lecture 2

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/80

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.

81 Terms

1
New cards

1960s and 1970s

The system development life cycle was started in ___ as the first documented approach to computer systems development

2
New cards

system development life cycle

The first documented approach to computer systems development

3
New cards

thought about, planned, monitored, and completed

All the stages of development system are ________, _________, _________, and __________

4
New cards

system development life cycle

the process by which an information system comes to life and maintains its usefulness to a business as it moves from inception to replacement

5
New cards

system development life cycle

a phased approach to solving business problems

6
New cards

system development life cycle

Developed through the use of a specific cycle of analyst and user activities

7
New cards

system development life cycle

Each phase has unique user activities.

8
New cards

1. identifying problems, opportunities, and objectives
2. determining information requirements
3. analyzing system needs
4. designing the recommended system
5. developing and documenting software
6. testing and maintaining the system
7. implementing and evaluating the system

phases in system development life cycle

9
New cards

1 identifying problems

interviewing user management

10
New cards

1 identifying problems

summarizing the knowledge obtained

11
New cards

1 identifying problems

estimating the scope of the project

12
New cards

1 identifying problems

documenting the results

13
New cards

2 determining information requirements

interviewing and questionnaires

14
New cards

2 determining information requirements

sampling and investing hard data

15
New cards

2 determining information requirements

observe the decision maker's behavior and environment

16
New cards

2 determining information requirements

prototype

17
New cards

2 determining information requirements

learn the who, what, where, when, how, and why of the current system

18
New cards

3 analyzing system needs

create data flow, activity, or sequence diagrams

19
New cards

3 analyzing system needs

complete the data dictionary

20
New cards

3 analyzing system needs

analyze the structured decisions made

21
New cards

3 analyzing system needs

prepare and present the system proposal

22
New cards

4 designing the recommended system

design procedures for data entry

23
New cards

4 designing the recommended system

design the human-computer interface

24
New cards

4 designing the recommended system

design system controls

25
New cards

4 designing the recommended system

design database and/or files

26
New cards

4 designing the recommended system

design backup procedures

27
New cards

5 developing and documenting software

system analyst works with programmers to develop any original software

28
New cards

5 developing and documenting software

works with users to develop effective documentation

29
New cards

5 developing and documenting software

programmers design, code, and remove syntactical errors from computer programs

30
New cards

5 developing and documenting software

document software with help files, procedure manuals, and web sites with frequently asked questions

31
New cards

6 testing and maintaining the system

test the information system

32
New cards

6 testing and maintaining the system

system maintenance

33
New cards

6 testing and maintaining the system

maintenance documentation

34
New cards

7 implementing and evaluating the system

train users

35
New cards

7 implementing and evaluating the system

analyst plans smooth conversion from old system to new system

36
New cards

7 implementing and evaluating the system

review and evaluate system

37
New cards

agile

iterative and flexible, emphasizing continuous feedback and adaptation

38
New cards

waterfall

sequential and rigid, focusing on thorough planning and execution in predetermined stages

39
New cards

agile approach

iterative, with regular feedback intervals

40
New cards

waterfall approach

linear and sequential

41
New cards

agile documentation

relies on minimal documentation, focusing on self-organizing teams, and collaboration

42
New cards

waterfall documentation

relies heavily on detailed documentation to ensure all team members are on the same page

43
New cards

agile flexibility

highly flexible and adaptable to changes during the development

44
New cards

waterfall flexibility

less flexible and resistant to change once the project scope is defined

45
New cards

agile communication

emphasizes information communication with frequent interactions between individuals or small groups of stakeholders

46
New cards

waterfall communication

communication is more formal, with detailed communication plans and progress reports

47
New cards

agile testing

emphasizes incremental testing throughout the development process

48
New cards

waterfall testing

typically does testing at specific milestones, often towards the end of the project

49
New cards

exploration
planning
iterations to the first release
productionizing
maintenance

Five stages of agile development

50
New cards

requirement analysis
system design
implementation
testing
development
maintenance
review (agile)
launch

agile and waterfall model

51
New cards

documentation is required

sdlc is best for projects where thorough __________ at every phase.

52
New cards

structured approach

sdlc is ideal when systems need to be developed and tracked using a _________.

53
New cards

predictability

sdlc is useful when upper-level management prefers _______ and formal processes.

54
New cards

enough time and resources

sdlc is suitable if the project has _________ to go through all SDLC phases.

55
New cards

clear communication

sdlc is recommended when ___________ of system functionality is a priority.

56
New cards

evolving or unclear

agile is best for projects with _______ requirements.

57
New cards

customer feedback

agile is ideal when collaboration and ________ are essential throughout the process.

58
New cards

rapid delivery

agile is useful when ________ of working software is a priority.

59
New cards

adapt quickly to change

agile is suitable for teams that can ________.

60
New cards

iterative cycles

agile is recommended when working in short, _______ is feasible

61
New cards

well-defined

waterfall is best for projects with ____, stable requirements.

62
New cards

unlikely to change

waterfall is ideal when the full scope is known upfront and ___________

63
New cards

extensive planning

waterfall is useful when _________ and documentation are critical.

64
New cards

linear and sequential

waterfall is suitable for teams following a _________ development process.

65
New cards

strict deadlines

waterfall is recommended when _________ and compliance are involved.

66
New cards

fishbone diagram

systematically lists all of the possible problems that can occur.

67
New cards

Albert Humphrey

Swot analysis technique is credited by __

68
New cards

swot analysis

A planning tool used to understand Strengths, Weaknesses, Opportunities, and Threats involved in a project / business.

69
New cards

swot analysis

Used as framework for organizing and using data and information gained from situation analysis of internal and external environment

70
New cards

job holder
business unit
company

who needs swot analysis?

71
New cards

fishbone diagram

systematically lists all of the possible problems that can occur

72
New cards

team management

  • assembling a team
  • team communication strategies
  • project productivity goals
  • team member motivation

managing analysis and design

73
New cards

task leader

leads members to accomplish tasks

74
New cards

socio-emotional leader

concerned with social relationships

75
New cards

training
experience
learning why other projects have failed

project failures may be prevented by:

76
New cards

evaluate real-world challenges
suggest IT solution
identify system requirements, constraints
incorporate suitable modeling tools and techniques
create project plans

importance of project proposal

77
New cards

evaluate real-world challenges

to identify opportunities for resolution through information technology and systems.

78
New cards

suggest IT solution

effectively tackle organizational issues and fulfill stakeholder requirements.

79
New cards

identify system requirements, constraints

Inventory management, e-commerce platforms, and customer relationship management depend on IT for operational efficiency.

80
New cards

incorporate suitable modeling tools and techniques

to design information technology solutions and project plans.

81
New cards

create project plans

clearly outline project goals, break down tasks, establish timelines, and define milestones for the successful execution of information technology projects.