C05

Question 1

System development:

Answer 1

Writing programs to fulfill the needs of users.

Question 2

For the development of systems to be successful, there needs to be:

Answer 2

• Well-defined system objectives.
• Careful test of feasibility.
• Support from top management.
• User involvement so that there is a strong commitment.
• Rigorous analysis to answer the user requirements are met.
• A good design that ensures an efficient, quality and maintainable system.
• Project management so that the team is managed and controlled.

Question 3

Systems Development Life Cycle (SDLC):

Answer 3

A process to build software applications that goes step by step. It is structured, rigid, not open to design changes, and designed for large projects.

Question 4

Systems Development Life Cycle: Phase 1:

Answer 4

Preliminary Analysis: Evaluating if the request is possible and needed, if there are alternatives. Then, a feasibility study is launched:

Needs analysis: If a request for a new system is needed.

Question 5

Systems Development Life Cycle: Phase 2:

Answer 5

System Analysis: Specific requirements with different stakeholders are determined. The Systems Analyst (person) documents the system requirements.

Question 6

Systems Development Life Cycle: Phase 3:

Answer 6

System Design: The specific technical requirements are determined: the user interface, database, data inputs and outputs, reporting = system design (created by Systems Analysis, Developer or Systems Architect) document (has everyone a programmer needs to create the system).

Question 7

Systems Development Life Cycle: Phase 4:

Answer 7

Programming: Software is developed using programming, coding = the first working program done by a Developer, Software Engineer or Coder.

Question 8

Systems Development Life Cycle: Phase 5:

Answer 8

Testing: Series of structured tests. First, unit test to test for bugs (code errors). Second, system test, testing every element in the system to make sure it works properly. All erors are resolved, and the system is tested again. Done by Tester, Testing Analyst, or Quality Assurance.

Question 9

Systems Development Life Cycle: Phase 6:

Answer 9

Implementation: Implemented in the organization. Training users, providing documentation, and converting data from the old system to the new system.

Question 10

Systems Development Life Cycle: Phase 7:

Answer 10

7. Maintenance: Bugs are fixed and new features evaluate and implemented. System updates and backups of the software when new versions of the program are developed.

Question 11

Waterfall methodology:

Answer 11

Another name for the SDLC because only once one step is done can the next one begin.

Question 12

Rapid Application Development (RAD):

Answer 12

Focuses on quickly building a working model of the software, gets feedback from users, and uses it to update the working model.

Question 13

Rapid Application Development (RAD): Phase 1:

Answer 13

Requirements planning: Overall requirements for the system is determined, a team is created and possibility (feasibility) is determined.

Question 14

Rapid Application Development (RAD): Phase 2:

Answer 14

2. User design: Analysts, designers and programmers create design of the system together.

Question 15

Rapid Application Development (RAD): Phase 2: Joint Application Development (JAD):

Answer 15

A structured discussion about the design of a system that brings all the stakeholders together.
- Sometimes it is used.

Question 16

Rapid Application Development (RAD): Phase 3:

Answer 16

3. Construction: Users and developers work together to create the next version of the system. Modifications are made until an acceptable version of the product is created.

Question 17

Rapid Application Development (RAD): Phase 4:

Answer 17

4. Cutover: Going for the old system to the new system. Each company has different implementation strategies.

Question 18

Traditional Project Management (TPM):

Answer 18

A method of developing projects that is structured.

Question 19

Agile Project Management (APM)

Answer 19

After every “short sprint” = getting feedback = then more development.
Requires users to be involved.

A flexible, iterative, and adaptive approach to managing projects. It emphasizes continuous improvement, flexibility, and rapid delivery.

Question 20

Lean methodology:

Answer 20

The goal of lean methodology is to optimize and streamline processes, reduce waste, and increase efficiency, quality, and customer value.

Question 21

Rapid Application Development (RAD):

Answer 21

The goal of RAD is to deliver a working product as soon as possible, with the idea that the users can then give feedback on the product, and the development team can make adjustments and improvements based on that feedback.

Question 22

Economic feasibility:

Answer 22

Does it make financial sense? Can we afford it?

Question 23

Technical feasibility:

Answer 23

Do we have enough hardware, software and personnel resources to support and develop the system?

Question 24

Operational feasibility:

Answer 24

Will it be accepted in the organization by management, and staff?

Question 25

System implementation: Direct cutover:

Answer 25

When the system is put into place fully and the old one is not used anymore. - Very fast, very risky: not able to turn back.

Question 26

System implementation: Pilot implementation

Answer 26

When the new system is given to a smaller group to use which helps problems be resolved before putting the new system throughout the entire organization.

Question 27

System implementation: Phased

Answer 27

Different functions of the new system is gradually implemented. Allows a company to move slowly from one system to another.

Question 28

System implementation: Parallel

Answer 28

When both the new system and the old system run at the same time which helps the new system to be tested. - Expensive

Question 29

Factors that lead to a project's failure:

Answer 29

- Unrealistic or unclear goals. - Poor leadership. - Bad estimates of needed resources. - Badly defined system requirements. - Poor reporting of the project's status. - Poor communication between customers, developers, and users. - Use immature technology. - Unmanaged risks. - Inability to handle the project's complexity. - Sloppy development and testing practices. - Poor project management. - Stakeholder politics. - Commercial pressures (causing not enough time and doing something in the cheapest way).

Question 30

PERT (Project Evaluation and Review Technique):

Answer 30

A project management tool used to plan, schedule, and control projects. breaking down the project into individual tasks, identifying dependencies between tasks, creating a network diagram to represent the tasks and dependencies, estimating the time it will take to complete each task, and determining the critical path (the sequence of tasks that will take the longest to complete). Best to identify bottlenecks and delays. A tool to figure out an estimation of project cost or time: optimistic + 4 * most likely + pessimistic)/ 6

Question 31

Critical Path:

Answer 31

The sequence of activities that takes up the most time to complete the project.

Question 32

Gantt:

Answer 32

A project management tool used to plan, schedule, and control projects. display the tasks of a project along a horizontal timeline, with the length of each task represented by a horizontal bar. Gantt charts are used to show the start and end dates of each task, the duration of each task, and the dependencies between tasks. Best to see the overall progress and to identify tasks that are running behind.

Question 33

Advantage of purchasing software from another company:

Answer 33

Less expensive. Available more quickly (can be up and running in a few days). Purchased package has already been tasted and bugs have been worked out.

Question 34

Disadvantages of purchasing software from another company:

Answer 34

- Can be used by competitors - no competitive advantage. - Customization - each time the software is updated, administrations need to manage their customizations - headache.

Question 35

Web services:

Answer 35

Web services: Allows companies to license functions without writing the code themselves. For example, a company using Google Maps in their application to show the location of someone who has called their support line.

Question 36

Quality triangle:

Answer 36

Time, Quality and Cost. Pick 2.

Question 37

IT Projects:

Answer 37

IT projects are projects that involve the design, development, implementation, or maintenance of information technology (IT) systems. IT projects can be large and complex, involving multiple teams and stakeholders, and often require careful planning, scheduling, and execution to ensure that they are completed on time and within budget.

Question 38

Risks for IT Projects:

Answer 38

- Good estimates are difficult because the technology is continually changing. - Lack of experience in the project team. - Lack of support from top management. - Lack of participation from system users. - Unclear and uncertain project requirements. - High level of technical complexity.

Question 39

Project manager:

Answer 39

Responsible for planning, organizing, and overseeing the work on a project to ensure that it is completed on time, within budget, and to the satisfaction of the stakeholders.

Question 40

Technical analyst:

Answer 40

Responsible for analyzing and interpreting complex technical data and information, and identifying trends, patterns and issues within them to make recommendations.

Question 41

Change management:

Answer 41

Managing the way change is implemented into an organization by communicating about the changes to employees, minimizing the impact of the change, training is given.

Question 42

System analyst:

Answer 42

Responsible for analyzing and evaluating complex systems and processes within an organization, and making recommendations for improving their efficiency and effectiveness.

Question 43

Business analyst:

Answer 43

Responsible for understanding the needs of the business and stakeholders, and using that knowledge to design, develop, and implement solutions that meet those needs and improve the efficiency and effectiveness of the organization.

Question 44

The Project Life Cycle

Answer 44

Initiate, planning, execution, close.