Topic 1

Part 1

SDLC and Structured Methodologies:

What is SDLC:

The Systems Development Life Cycle (SDLC) is a conceptual model used in project management that
describes the stages involved in an information system development project, from an initial feasibility
study through maintenance of the completed application.

What is Structured Methodologies:

Are traditional information system development methodologies. They have very detailed steps
explained everything within them. We always make sure the that the requirements are clear and fixed if
using any structured methodology due to the rigidity and strict rules. Traditional methodologies ensure
a full documentation as well as focusing on the error-free product. There are a lot of structured
methodologies such as waterfall, v model and so on.

Case study is given; couple of stakeholders, and we need to develop an information system, and one
stakeholder disagrees with the structured way. We are asked our opinion on whether we can use the
SDLC approach and how is it different from the structured methodology (any structured method)

Part 2

Same case study, why is the structured methodology appropriate

All structured methodology has clear and simple stages which developers can easily go on it and apply
them. their simplicity makes the understandable by a wild range of people. The structured methodology
emphasis a full documentation system development and they also focus on product quality as well as
process quality. Using structure methodology grant you an application working that is delivered on time
as agreed in the early stages. Since the requirements are clear and nothing expected to need a change,
in this case, structure methodologies will fairly work appropriate.
Part 3

What methodology would you suggest for the development and why.

Based on the requirements:

let's assume that the project has a big database. I would like to recommend my team to approach scrum
due to many reasons, as the following.

1. Scrum is an agile methodology which means it concerns on customer satisfaction and it uses
latest technology techniques.

2. Scrum involves the client as one of the important characters in the development cycle. The
product owner(client) has the power to change his mind at any stage of the development
period.

3. As there are many people involves in the project, Scrum is suitable cause it makes sure about
close communication and teamwork

Part 4

Explain any one of the modern methodologies, explain iterative and incremental approach:

Rapid Application Development (RAD). By looking at this methodology name, it is clear that it is fast in
which used for fast and urgent projects. The development of the system can be last within days or
weeks depending on the complexity. RAD has four stages as the following diagram shows.
Topic 2

Part 1

Explain briefly on design models

A design model is an object model that is used to describe the realization of use case and it also serves
abstraction of the implementation model. The design model is essentially used as input to activities in
the implementation and test. for example, UML stereotypes as the design model.

UML

It is a shortcut for unified modeling language. It is basically a modeling technique in which used to
visualize the design of the system. UML supports OODA. and it can be used for many purposes for
example, designing, discussing, presenting and testing a particular software. UML has two different
views as the following.

1. Static view: Emphasis the static structures of the system. Used for data and process oriented
development approach.

2. Dynamic view: Emphasis the dynamic behavior of the system. Used for the user and some
process-oriented development approach.

UML involves many tools such as the use case diagram and activity diagram.

Part 2

What is a risk management:

It is the process of identifying the potential risk to the project and getting prepare for it. For example,
many projects fail because of the development team does not identify the risk possibilities or even
ignoring risks, therefore it is an essential step to be done and risks in the project must be identified

Risk management strategies, 2 examples:

1. Risk transfer: accepting the risk, transferring that risk to a vendor or customer who is willing to
face it.

2. Risk avoidance: Accepting the risk, taking an alternative path to avoid the risk of happening.
Changes may occur in the design.

3. Risk reduction: accepting the risk, taking additional steps to reduce the risk from happening
(cost may increase).

Part 3

Suggest a methodology suitable for the case study and justify it

Topic / 03

Part 1

Differences between AGILE and Traditional development methods

Agile:

 It involves modern technology such as Scrum and so on.

 It was developed in the mid-80's.
 It's focus on fast delivery of the software and customer satisfaction.
 It has flexible stages and it welcome changes. Besides, it adopts agile principles.

Part 2

Why has AGILE become popular?

Agile become popular due to the advantages that are given to its users. We summarize these
advantages into the following points.

1. Agile ensures customer satisfaction.

2. Agile given the users the power to change their minds at any stage of the development process.

3. Agile is flexible and it welcomes new requirements and changes.

4. Agile gives controls to the developers to make the decision.

5. Agile approach latest technology techniques.

6. Agile concerns on teamwork and its emphasis close communication

Topic 4

Part 1

Development Stage:

During this stage, the system is constructed via a programming language. The development stage takes
place when the design of the system is approved and design specification is available. The output of this
stage is a fully working software. However, before coding the development team must look at few things
and keep them in consideration such as:

 The choice of programming language.

 Following the coding standards.
 The choice of types of testing to be carried out.
 Looking at code repository, security, and copyright.
 Ensuring that the team will approach, good programming practices such as having a readable
code.

After the construction of the system, it is the right time for the system to be tested which you have two
approaches.

1. Static (Without execution).

2. Dynamic (With execution).

What factors would you consider while hiring a new developer:

 Communication skills.
 Technical expertise and knowledge.
 Qualifications.
 Interviewing him\her.
 Experience and skills.
 His\her past projects.

What is a Version controls:

It is one of the coding strategies that programmers must keep in consideration before starting the
construction of the system. Version control holds the responsibility for control of modifications made on
the code and it back up and it stores workable code.
What are the Programming standards and good practices:

 Ensure the efficiency of the code: Keep the code short and simple.
 Portability: Use good variables naming and avoid hand codes.
 Security: Secure source codes, Encapsulation.
 Ensuring readable code: neat and clears code.
 Refactoring: make sure that the code is capable of having it refactors.

What is Security copyright:

 It is a coding strategy in which ensures applying a fain level of security to the code.
 considering the artifacts that needed to be controlled / copyright

Part 2

What is Testing:

Software testing is the process of executing an application with the intent of finding any error inside that
software.

What strategies that you would consider to do an efficient test:

Initially, our team will implement static testing to the system, static testing is that type of test that gets
done to the system while the system is not executed. The purpose of this type is to verify requirements.
Many techniques included here such as reviewing documents static analysis, walkthrough, inspection
and so on.

Then the team needs to run the software and implement dynamic testing to it. The dynamic testing
takes a place during the validation process. Dynamic testing includes unit, integration, and system
testing as the following:

 unit testing: test system components one to one.

 integration testing: make sure that all the connections between the system components are
fine.
 System testing: test a completely integrated system and make sure all the requirements are
there in the system.
Part 3

What is a Test plan:

It is a technique that is used by software testers as a guide to test a software. The test plan uses
"dummy data" that is prepared before the software is built by software testers.

What are the things you would include on your test plans:

 Test cases: the set of conditions or variables in which a tester will determine a system under test
satisfies requirements
 Session bases test management: test method aims to combine accountable and exploratory
testing to rapidly discover defects.
 test management tools: tools have different approaches to testing and therefore have different
sets of features
 checklists: the catalog of items or tasks that are recorded for tracking.
 mind maps: diagrams of relationships between concepts, idea, or any other information.

Who are the testers:

Depending on the testing type approach, it may be the programmer, users, or IT department.

What output you are expecting:

 Giving an accurate estimation of the release date.

 Giving definitive enhancement bugs list.
 determine how far the requirement is being implemented.
 Causes software quality
Topic 5

Part 1

What is the software deployment?

It is the act of releasing a software into the market in which that system is ready to be used.

What are the factors would you consider while thinking of deployment?

 Determine a deployment option.

 Package software.
 The time that the software is going to be deployed.
 Determining a system change over the strategy based on the previews system for the client.
 Integrating system components.
 Getting the post. Deployment Testing is done.
 Provide training to those who are going to use the system.

What is a Packaging software:

It is a system deployment plan in which the deployment team determines and specify how the system
components are going to be delivered to the users (Stakeholders).

Who is getting involved in the system deployment:

The development team.

Explain the various Changeover strategies:

1. Direct Cutover: Replacing the old system with the new system when the new system is ready to
be used.
2. Parallel Operation: Making both old and new system work simultaneously until it is time to
completely depend on the new system.
3. Pilot Operation: Try the new system on one of the company branches to make sure it functions
well before completely depend on the new system.
4. Phased Operation: Gradually replacing the old system with the new system.

Part 2
Problems during deployment

 Insufficient time
 Users are not compatible
 Failures may come about
 Testing not done properly
 Inexperienced users

Part 3

Changeover Methods

Suggest one based on case study and explain how it is carried out

Direct cutover

Pilot

Parellel

Phased