Software development methodologies.

Rational unified process (RUP), UML,

Business modeling tools
Requirements management tools
Automation tools
Visual modeling tools
Testing tools
Change management tools
Reporting tools
SEI-CMM
Rational rose, MS visio, MS Project.
Rational requisite pro
Rational robot, test manager, Win runner,
Load runner.
Rational rose, MS visio, Snag IT
Win runner, QTP
Rational clear quest
Crystal reports, SODA.

 Rational Tools 
RUP E-coach Process and templates
Rational rose Modelling
Rational requisite pro Requirement gathering
Rational clear case Configuration management
Rational clear quest Change management
Rational test director testing

 BRD (Business requirement diagram) 

Project name: abcd….

Current version  
Owner  
Date last updated  
Last updated by  
Author  
Date created  
Approved by  
Approved date  

 Revision History
 

Version no Date updated Revision author Brief description of

change
       
  What is flow chart and its uses
A flowchart is very simply a diagrammatic representation of the flow of information. Now this
flow of information could be in a Information Processing System or just an explanation of how
an algorithm works.  A flowchart typically shows the flow of data in a system, detailing the
operations in a pictorial format which is easier to understand than reading it in a textual format.
Besides, a flowchart quite simplistically shows the sequence of the operations taking place in the
system too.

Hence a flowchart helps in solving a problem by offering an easy to understand graphical

solution that shows the different operations which are the steps of the solution and the sequence
of those operations.  Hence a flowchart is used extensively in IT and ITES companies. A
flowchart can be compared to the blueprint of a building. It shows what the structure of the
building is (or algorithm or problem or the information processing system) and shows the
building blocks of the structure which comprise the information needed to arrive at the solution
through sequential blocks of data. It wouldn’t be wrong to say a flowchart is a sort of a ‘must’ to
document and explain complex and lengthy programs.

A flowchart has certain rules that need to be followed while drawing it. These rules are given by
a governing body known as the ANSI (American National Standard Institute). There are certain
standard ways of drawing a flowchart with the symbols prescribed by ANSI. Knowledge of these
symbols is necessary if u want to draw a flowchart. These flowchart symbols are given below

The rectangle in a flowchart denotes processing function or a just a computational step while
processing.

The oval is used to denote start or end of a program.

 The parallelogram is used to denote the input or output steps of a program

           

                                                                

Connector in a flowchart

This is used to denote a magnetic tape.

This is used to denote a magnetic disk.

This is used to denote an off-page connector.

  

This is used to denote “ Display “

These arrow lines are called flow lines.

    

These are the basic symbols used generally. Now, the basic rules for drawing a flowchart with
the above symbols are that:

  The flowchart is to be read left to right or top to bottom.

  A process symbol can have only one flow line coming out of it.

  For a decision symbol, only one flow line can enter it, but multiple lines can leave it to
denote possible answers.

  The terminal symbols can only have one flow line in conjunction with them.

A simple example of a flowchart of a purchase and quality inspection routine is below:

  What is GAP analysis
Gap Analysis:
1        The process of determining, documenting, and approving the variance between business
requirements and system capabilities.
2        The process of determining and evaluating the variance or distance between two items’
properties being compared.
3        The study of the differences between two different systems or applications, often for the
purpose of determining how to get from one state to a new state.
4        A gap is sometimes spoken of as "the space between where we are and where we want to
be." Gap analysis is undertaken as a means of bridging that space.

 Usecase template with example

Author:  David ryan                                                                  Date: May 7th,
2007.                                                                                                               Version :1

Use case name ATM USE CASE type

Use case id ATM-W
Priority High Business requirements : yes.
Source Requirement-RATM-W
Primary business actor Customer/bank account/Card holder.
Other participating actors Bank
Description The use case describes the withdrawl process of money from a ATM.
It contains various steps that involve the verification of customer
card and processing and generating receipt and giving money.
Pre condition The customer withdrawing money should have a bank account and a
valid card.
Trigger The use case will be initiated when the user inserts card in the slot.
Typical flow of events Actor Action System Response

Step 1: The customer inserts the Step 2: The system will check
card. the validity of the card and will
prompt for PIN no.
 
 
Step 3: The customer will enter
the PIN. Step 4: The system will check
the database and validates the
PIN no & customer acct.

Step5: Bank database confirms

 the correctness.

Step6: ATM asks the customer to

enter the amount to be
withdrawn.

Step7: Amount verified against

the balance in cust acct.

Step8: ATM dispenses the

amount

Step9: Receipt is printed.

Step10: Card is ejected.

Alternate cources Alt step 2: If the customer inserts a invalid card or improper
insertion then system prompts a message to customer.
  Alt step 3: Customer enters wrong pin, then system will show a error
message.
  Alt step 4: If the amount entered is more than balance them system
shows a message.
Conclusion The use case concludes when the card is taken out of the slot.
Business rules  The customer has a valid card with a bank account in the
bank.
 The machine has sufficient amount.
 The amount to be withdrawn is with in the limits set for a
day.
 There is sufficient amount left in the account.(minimum
required)

 Usecase example
 Ucd id:                A.1

  

 Use case Name:  Get paid for travel expense.

  

 Objective:           Getting paid for travel expenses.

 Primary actor :  The person who claims.

  

 Scope:                   The Accounting department.

  

 Stakeholders:        1. Claimant: (purpose: to get paid the max amount).

                               2. Accounts department (Purpose : To pay the minimum possible).

  

 Trigger                :  The claimant submits(fires the event) the claim, (claim for travel

                                   reimbursement)

  

 Success scenario:   1. Claimant submits the claim with data.

                                2. Accounts department checks(validate) the submitted bills.

                                3. Department person verifies all bills if they are correct.

                                4. Accounts dept pays the claims.

  

 Failure scenario:     1. Submitted data is not complete.

                                     Solution: Accounts dept requests for missing data and claimant

                                     submits the same.

                                 2. Claimant does’t authorize to claim the travel expense.

                                    Solution: Accounts dept declines the claimant and stops all

                                     processing.

                                 3. Travel violates basic traveling policies.

                                      Solution: Acounts dept declines the process.

   

 What is JAD session

JAD session:
1        It brings together business area people (users) and IT (Information Technology)
professionals in a highly focused workshop.
2        JAD participants typically include:
o Facilitator – facilitates discussions, enforces rules
o End users – 3 to 5, attend all sessions
o Developers – 2 or 3, question for clarity
o Tie Breaker – senior manager. Breaks end user ties, usually doesn’t attend
o Observers – 2 or 3, do not speak
o Subject Matter Experts – limited number for understanding business & technology
3        Advantages:
o Shortening of the time.
o Improves the quality of the final product by focusing on the up-front portion of the
development lifecycle.
o Reducing the likelihood of errors that are expensive to correct later on.

 Bug life cycle in testing

If a bug comes, we open the bug issue. It should look like below.

Open the Issue (bug/defect)

Delegate the bug/issue/

        If from business side, then send to business dept.

        If from IT site then send to Technical dept.

Resolve the bug by assigning it to concern developer.

Withdraw.

Finally Close the bug.

Test director is a good reporting tool used for generating the test reports.

 What is RUP (rational unified process)? 

RUP stands for Rational Unified Process. Its a software development process framework which
has been taken forward by Rational(part of IBM corporation)

Its a proper guidelines to be followed so to achieve standardization and improvement of the

existing processes. RUP has phases and iterations which have to be followed with the help of
templates and guidelines implemented at each stage. The intention of  usage of RUP is to provide
standards for all stages of the software development life cycle. RUP is supported by different
tools and methodologies among which is Rational's UML(Unified Modeling Language).

In the figure, the Rational Unified Process Model can be diagrammatically viewed. As depicted,
RUP has four distinct project life cycle phases:

a) Inception – is the part where the actual exploration of the concept happens with the
stakeholders management, definition of the project scope, cost benefit and feasibility analyses.
This is the starting phase of the project and actually provides the foundation for each of the
ensuing processes.

b) Elaboration – This is the phase where the project starts to take shape. The requirements are
more or less frozen and the design of the system gets into its first draft.

c) Construction – This phase is the actual building phase of the project where the software takes
shape and it involves the major coding part out of the four phases. Testing is also part of this
phase. The first cut release of the software is the objective of the phase
d) Transition – This phase is the wrapping up of the system with the release to the client and the
final support phase of the software system starts.

 RUP also has six engineering disciplines and three supporting disciplines. These nine RUP
disciplines are part of each iterations required in the project life cycle. The six engineering
disciplines are somewhat similar to the waterfall model phases whereas the three supporting
disciplines are unique to the RUP framework.

I. RUP Engineering Disciplines

a) Business Modeling – Initial modeling of business with the analysis and scope formation

b) Requirements – gathering and communication of requirements

c) Analysis and design – analysis and formation of the solutions designs

d) Implementation – Implementing the solution

e) Test – testing the system as a whole and in units

f) Deployment – finally deploying the system at client site and going into production level

II RUP Supporting Disciplines

a) Configuration and Change Management – configuration of the versions of documents and

code. Management of changes to requirements, solution and codes as required

b) Project Management – Planning, estimation, resourcing and overall managing the team and
customers as part of the project

c) Environment -  Ensuring that the project team is aware of all aspects and of the RUP
implementation.

Fig A – The Rational Unified Process Model

As per the Fig A , the RUP framework is depicted as a “hump chart” with the matrix showing
the RUP phases and the RUP disciplines. Lets say for example, the requirement discipline is
peaked at the initiation and elaboration stage after which it flattens bout does not completely
disappear. Similarly project management discipline is required to be at a constant peak
throughout the project and cannot flatten or lag behind in any phase.

RUP is one of the most complex software development project life cycles and involves proper
project planning for the successful implementation of the system

 What are Deliverables in RUP and phases

 Inception phase:  Project plan, BRD, High level usecases.

 Elaboration:       UML diagrams, Change management & config management.

 Construction:  System code, QA testing cases, / test scripts, and a test plan.

 Transition:   Product delivery, Project documentation.

 Who are Business users of the system