Roch, S., Fowler, J., Smith, B. & Bourgeois, D. (2022). Information Systems for Business and Beyond. Chapter 7: Systems development.

Question 1

(Roch, S. Chapter 7: Systems development)

What is Systems Development?

Answer 1

System development could be seen as the simple process fo writing programs to solve the needs of users. However, in reality this process is not that simple. End users ma know whta they want, but lack the technical expertise to bring the idea to life. Also, programmers may understand the computer, but not the user environment. Thus communication gap between the user and the service provider must be addressed. Using a systems development methodology can help mitigate these challenges and support development success. Pressure for rapid development and future maintainability of systems has resulted in a number of alternative approaches to systems development, ranging from development by end-users, to the incorporation of formal methods to improve the quality and efficiency of the development process.

Question 2

(Roch, S. Chapter 7: Systems development)

What is System Development Life Cycle (SDLC)?

Answer 2

This approach to software development is structured and risk averse, designed to manage large projects that include multiple programmers and systems. It requires a clear, upfront understanding of what the software is supposed to do and is not amenable to design changes.

Question 3

(Roch, S. Chapter 7: Systems development)

System Development Life Cycle (SDLC): 1. What happens in Preliminary Analysis Phase ?

Answer 3

1. Preliminary AnalysisA request for a replacement or new system is first reviewed. The review includes questions such as: What is the problem-to-be-solved? Etc. This proves is referred to as a needs analysis.

Question 4

(Roch, S. Chapter 7: Systems development)

System Development Life Cycle (SDLC): 2. What happens in System Analysis Phase ?

Answer 4

2. System Analysis
   In this phase one or more system analysts work with different stakeholder groups to determine the specific requirements for the new system. No programming is done in this step. –> Procedures are documented, key players7users are interviewed, and data requirements are developed in order to get an overall impression of exactly what the system is supposed to do.

Question 5

(Roch, S. Chapter 7: Systems development)

System Development Life Cycle (SDLC): 3. What happens in System Design Phase ?

Answer 5

3. System Design
   A designer takes the system requirements document created in the previous phase and develops the specific technical details required for the system. Business requirements are translated into specific technical requirements. The result is a system design document. This has everything a programmer needs to actually create the system.

Question 6

(Roch, S. Chapter 7: Systems development)

System Development Life Cycle (SDLC): 4. What happens in Programming Phase ?

Answer 6

4. Programming
   The. Ode finally gets written in the programming phase. Using the system design document as a guide, programmers develop the software.

Question 7

(Roch, S. Chapter 7: Systems development)

System Development Life Cycle (SDLC): 5. What happens in Testing Phase ?

Answer 7

5. Testing
   In the testing phase, the software program developed in the programming phase is put through a series of structured tests. First unit test (individual parts of code) and then system test (different components of the system) and lastly the user acceptance test.

Question 8

(Roch, S. Chapter 7: Systems development)

System Development Life Cycle (SDLC): 6. What happens in Implementation Phase ?

Answer 8

6. Implementation
   Once the new system is developed and tested, it has to be implemented in the organization. This phase includes training the users, providing documentation, and data conversion from the previous system to the new system.

Question 9

(Roch, S. Chapter 7: Systems development)

System Development Life Cycle (SDLC): 7. What happens in Maintenance Phase ?

Answer 9

7. Maintenance
   In this phase the system has a structured support proved in place. Reported bugs are fixed and system updates and backups are made.

Question 10

(Roch, S. Chapter 7: Systems development)

System Development Life Cycle (SDLC): Facts about it?

Answer 10

The SDLC methodology is sometimes referred to as the waterfall methodology to represent how each step is a separate part of the process. Only when one step is completed can another step begin. After each step an organization must decide when to move to the next step.
 Rigid/inflexible
 Allowing movement in only one direction (forward)
 Changes to the requirements are not allowed once the process has begun
 Big projects

Question 11

(Roch, S. Chapter 7: Systems development)

System Development Life Cycle (SDLC): Facts about it?

Answer 11

The SDLC methodology is sometimes referred to as the waterfall methodology to represent how each step is a separate part of the process. Only when one step is completed can another step begin. After each step an organization must decide when to move to the next step.
 Rigid/inflexible
 Allowing movement in only one direction (forward)
 Changes to the requirements are not allowed once the process has begun
 Big projects

Question 12

(Roch, S. Chapter 7: Systems development)

What is Rapid Application Development (RAD)?

Answer 12

RAD focuses on quickly building a working model of the software, getting feedback from users, and then using that feedback to update the working model. After several iterations of development, a final version is developed and implemented.

Question 13

(Roch, S. Chapter 7: Systems development)

Rapid Application Development (RAD): what happens in Requirements planning phase?
´

Answer 13

1. Requirements planning
   Similar to the preliminary analyses, system analysis, and design phases of SDLC.
   Overall requirements for the system are defined, a team is identified, and feasibility is determined

Question 14

(Roch, S. Chapter 7: Systems development)

Rapid Application Development (RAD): what happens in User design phase?

Answer 14

2. User design
   In the user design phase representatives of the userts wotk with the system analysts, designers, and programmers to interactively create the design of the system. Sometimes a Joint Application Development (JAD) session is used to facilitate working with all of these various stakeholders. A JAD session brings all of the stakeholders for a structured discussion about the design of the system together.

Question 15

(Roch, S. Chapter 7: Systems development)

Rapid Application Development (RAD): what happens in Construction phase?

Answer 15

3. Construction
   Application developers, working with the users, build the next version of the system through an interactive process. This step is executed in paralleled with the user design step in an iterative fashion, making modifications until an acceptable version of the product is developed.

Question 16

(Roch, S. Chapter 7: Systems development)

Rapid Application Development (RAD): what happens in Construction phase?

Answer 16

3. Construction
   Application developers, working with the users, build the next version of the system through an interactive process. This step is executed in paralleled with the user design step in an iterative fashion, making modifications until an acceptable version of the product is developed.

Question 17

(Roch, S. Chapter 7: Systems development)

Rapid Application Development (RAD): what happens in Cutover phase?

Answer 17

4. Cutover
   This involves switching from the old system to the new software. Timing of the cutover phase is crucial and is usually done when there is low activity. Approaches to the migration from the old system to the new system differ: Hard cut/incremental cutover/one part at a time.

Question 18

(Roch, S. Chapter 7: Systems development)

Rapid Application Development (RAD): what is RAD methodology ?

Answer 18

RAD methodology
 Focus on user participation and iteration
 Much better for smaller projects and projects that need to be developed quickly
 Less resource intensive than SDLC

Question 19

(Roch, S. Chapter 7: Systems development)

What are Agile Methodologies?

Answer 19

Agile Methodologies
Methodologies that utilize incremental changes with a focus on quality and attention to detail. Each increment is released in a specific period of time, creating a regular release schedule with very specific objectives. While considered a separate methodology from RAD, the two methodologies share some of the same principles such as iterative development, user interaction, and flexibility to changes.

The diagram above above emphasizes iterations in the center of agile development. You should notive how the building blocks of the developing system move from left to right, a block at a time, not the entire project! Blocks that are not acceptable are returned through feedback and the developers make the needed modifications. The daily review at the top of the diagram implies constant evaluation by both developers and customers (collaboration) of each day’s work.

 Small cross-functional. Teams that include developments team members and users
 Daily status meetings to discuss the current state of the project
 Short time-frame increments for each change to be completed

Question 20

(Roch, S. Chapter 7: Systems development)

What is Lean methodology?

Answer 20

Lean focuses on taking an initial idea and developing a Minimum Viable Product (MVP). The MVP is a working software application with just enough functionality to demonstrate the idea behind the project. Once the MVP is developed, the development team gives it to potential users for review. Feedback on the MVP is generated in two forms:
1. Direct observation and discussion with the users and second
2. Usage statistics gathered from the software itself
Using these two forms of feedback, the team determines whether they should continue in the same direction or rethink the core idea behind the project, change the functions, and create a new MVP. Several iterations of the MVP are developed, with new functions added each time based on the feedback, until a final product is completed
The biggest difference between iterative and non-iterative methodologies is that the full set of requirements for the system are not known when the project is launched.
 Lean methodology works best in an entrepreneurial environment where a company is interested in determining if their idea for a program is worth developing

Question 21

(Roch, S. Chapter 7: Systems development)

What is End-User Computing (EUC)?

Answer 21

End-User Computing (EUC)
People who build department-specific applications are not necessarily trained in programming or application development, but they tend to be adept with computers.
A person who is skilled in a particular program may be called upon to build smaller applications for use by their own department. This phenomenon is referred to as end-user computing.
 Brings development of applications closer to those who will use them
 IT departments sometimes backlogged thus providing a means to have software created more quickly
Also disadvantages
 If departments within an organization are developing their own applications, the organization may end up with several applications that perform similar functions (inefficient –> duplication of efforts)
 May provide different results

Question 22

(Roch, S. Chapter 7: Systems development)

What is Feasibility?

Question 23

(Roch, S. Chapter 7: Systems development)

What is Feasibility?

Answer 23

In order to ensure that the news system would be of a greater benefit to the organization than other competing requests for proposals, a feasibility study must be performed covering the following three major areas: economic, technical and operational feasibility.

Question 24

(Roch, S. Chapter 7: Systems development)

What is Economic Feasibility?

Answer 24

to measure the costs and benefits of new systems

Question 25

(Roch, S. Chapter 7: Systems development)

What is Technical Feasibility?

Answer 25

to ensure that the organisation has sufficient hardware, software and personell resources to develop and support proposed system

Question 26

(Roch, S. Chapter 7: Systems development)

What is Operational Feasibility?

Answer 26

the willingness and ability of management, user and information systems staff in the organisation to build and use proposed system

Question 27

(Roch, S. Chapter 7: Systems development)

What is the quality triangle?

Answer 27

Time, Quality and cost

-> When developing a software, a tension exists between the developers and the different stakeholder groups. This tension relates to how quickly the software can be developed (time), how much money will be spent (cost), and how well it will be built (quality). The quality triangle is a simple concept. It states that for any product or service being developed, you can only address two of the following: time, cost, and quality (if a project should be high quality and short timeframe you have to pay a lot).

Question 28

(Roch, S. Chapter 7: Systems development)

What does design mean for information systems?

Answer 28

The key to successful information systems is good design –> If the design doesn’t satisfy the business need, then what’s the point?
The following characteristics should be considered in the design proves:

Question 29

(Roch, S. Chapter 7: Systems development)

What does design mean for information systems: Usability?

Answer 29

 Usability
Describes how easy the system is to navigate

Question 30

(Roch, S. Chapter 7: Systems development)

What does design mean for information systems: Graphic design?

Answer 30

 Graphic design
Refers to the visual appeal and organization of the user interface. There is obviously some overlap with usability. However, a usable system could be bland and uninteresting.

Question 31

(Roch, S. Chapter 7: Systems development)

What does design mean for information systems: Analytical design?

Answer 31

 Analytical design
Describes how to best represent information – especially quantitative information – to communicate clearly and truthfully.

Question 32

(Roch, S. Chapter 7: Systems development)

What is the difference in Building A Mobile App compared to application for computer?

Answer 32

Building an application for a mobile device is mostly the same as building an application for a computer. But there are five primary differences:
Breakthroughs in component technologies, sensors have unlocked the notion of context, Simple, purpose-built, task-oriented apps are easy to use, Immediate access to date extends the value proposition, App stores have simplified acquisition, Responsive Web Design (RWB

Question 33

(Roch, S. Chapter 7: Systems development)

What is the difference in Building A Mobile App compared to application for computer: Breakthroughs in component technologies?

Answer 33

Mobile devices require multiple components that are not only smaller but more energy-efficient that those in computers.

Question 34

(Roch, S. Chapter 7: Systems development)

What is the difference in Building A Mobile App compared to application for computer: Sensors have unlocked the notion of context?

Answer 34

Sensors have unlocked the notion of context
Sensors like GPS/cameras enable devices to be aware of things like time, location.

Question 35

(Roch, S. Chapter 7: Systems development)

What is the difference in Building A Mobile App compared to application for computer: Simple, purpose-built, task-oriented apps are easy to use?

Answer 35

3. Simple, purpose-built, task-oriented apps are easy to use
   They need to be intuitive and not require any training

Question 36

(Roch, S. Chapter 7: Systems development)

What is the difference in Building A Mobile App compared to application for computer: Immediate access to date extends the value proposition?

Answer 36

Immediate access to date extends the value proposition
Having access to the cloud is needed to keep mobile device size and power use down.

Question 37

(Roch, S. Chapter 7: Systems development)

What is the difference in Building A Mobile App compared to application for computer: App stores have simplified acquisition?

Answer 37

siehe summary

Question 38

(Roch, S. Chapter 7: Systems development)

What is the difference in Building A Mobile App compared to application for computer:Responsive Web Design (RWB)?

Answer 38

Focuses on making web pages render well on every devise

Question 39

(Roch, S. Chapter 7: Systems development)

What is Programming?

Answer 39

Programming is the process of creating a set of logical instructions for a digital device to follow using a programming language. Programming language is an artificial language that provides a way for a developer to create programming code to communicate logic in a format that can be executed by computer hardware.

Question 40

(Roch, S. Chapter 7: Systems development)

Programming: What is First-generation language?

Answer 40

First-generation language is called machine code –> setting actual numbers as codes

Question 41

(Roch, S. Chapter 7: Systems development)

Programming: What is The second-generation language?

Answer 41

The second-generation language is called assembly language –> uses English-like phrases rather than only number instructions, making it easier to program. The assembly language program must be run through an assembler, which converts it into machine code.

Question 42

(Roch, S. Chapter 7: Systems development)

Programming: What is The third-generation language?

Answer 42

Third-generation language is called source code –> similar to spoken language

Question 43

(Roch, S. Chapter 7: Systems development)

Programming: What is The Forth-generation language?

Answer 43

Fourth-generation language enable fast application development using intuitive interfaces and environments.

-> Lower-level languages are much more efficient and executive much more quickly. The developer has finer control over the hardware as well.

Question 44

(Roch, S. Chapter 7: Systems development)

Buy or Build: Advantages to purchasing software from outside?

Answer 44

Advantages to purchasing software from an outside company
 Less expensive
 Available much more quickly
 Purchased package has already been tested/most bucks have already been worked out

Question 45

(Roch, S. Chapter 7: Systems development)

Buy or Build: Disdvantages to purchasing software from outside?

Answer 45

Disadvantages to purchasing software from an outside company
 Same software can be used by competitors
 Process of customization –> manage customizations every time the vendor provides an upgrade

Question 46

(Roch, S. Chapter 7: Systems development)

Types of Implementation and maintenance?

Answer 46

There are several methodologies an organization can adopt to implement a new system:
1. Direct cutover
2. Pilot implementation
3. Parallel operation
4. Phased implementation

Question 47

(Roch, S. Chapter 7: Systems development)

What are the most common factors for failing?

Answer 47

The most common factors for failing include:
 Unrealistic/unclear project goals
 Poor project leadership/weak executive commitment
 Inaccurate estimates
 Poor reporting of the project’s status
 Sloppy development and testing practices
 Use of immature technology

-> Astonishing one in three technology development projects fails to be successfully deployed.

Question 48

(Roch, S. Chapter 7: Systems development)

what is Maintenance?

Answer 48

Changes need to be made when bugs are found or new features are requested. During this phase, IT management must ensure that the system continues to stay aligned with business priorities and continues to run well.