Currently I am working as UID professional fr the current 
project. My responsiblity includes designing User 
interfaces and task analysis.

My responsibilities in this project included 

Development of Customer, Tracker and Downloads module. 
Involved in development, debugging, and Unit Testing

Testing (specially Unit testing) and peer code review

We ensure quality of code by doing
1)Self code review
2)Peer to peer code review.
3)Adher to different coding standards
4)Follow best cdoing practices.
5)Ensure right code version by making CM audit check list.

Sequence diagram is basically a flow chart w.r.t time.
However, a collabration diagram is very much the sequence
diagram without any time. Collaboration diagrams basically
shows the interaction of the various objects.

A sequence diagram shows object interaction arranged in 
time sequence. It depicts the objects and classes involved 
in the scenario and the sequence of messages exchanged 
between the objects needed to carry out the functionality 
of the scenario. While a collaboration diagram is an 
alternative way to show a scenario. Object interactions are 
organised around the objects and their links to each other. 
A collaboration diagram contains: - objects drawn as 
rectangles, links between objects shown as lines connecting 
the linked objects, messages shown as text and an arrow 
that points from the client to the supplier

1. Waterfall
2. RUP (Iterative)
3. eXtreame Programming (Agile)
4. some others like Sprial, V-Shape etc.

also include RAD model in the above answer

1.waterefall model
2.prototyping model
3.iterative enhancement model
4.RAD model
5.spiral model
6.component based devlopment model(cbd model)
7.time boxing model e.t.c

waterefall model
2.prototyping model
3.iterative enhancement model
4.RAD model
5.spiral model
6.component based devlopment model(cbd model)
7.time boxing model e.t.c
8.MVC Model

Tell something .
Client/Server architecture (r ) Two tier (r) Three tier .
.Net also max 3 tier project.
Check the answer.

HI ,
I am narasimha,plz go through this link.


http://www.c-
sharpcorner.com/UploadFile/paulabraham/Building3TierAppPA112
82005053625AM/Building3TierAppPA.aspx

First approach must be to break your code. Write the
testcase with wrost condition first and best condition later.

i am write test very well and don't copy from other
whatever you know write the test.

Both the above answers are wrong.

Unit test cases are normally not written after coding but 
they are written before coding.

So, break up the functionality into smallest pieces like 
each broken piece of functionality can accept an input 
criteria as well as output criteria.

Req needs to matched with existing projects. Look into the
existing code and database for the same.

The current requirement will be analyzed on feasibility 
point of view that what may happen when a particular amount 
of changes will be done in current system and whether it 
will effect any current feature or not. If yes then upto, 
which extent.
In general while incorporating changes impact will be 
observed by seeing base line effects.

We can follow these steps:
#1. First need to understand changes (X changes)
#2. Areas it effects (changes in development / architecture
or just a new step) (n places)
#3. Update your traceability for functionality associated
with changes (existing requirements +/- x*n additional changes)

A CR is raised, followed by TIME and COST. Finally, need to
agree on some date and then carry on with usual process.

We need to follow following list of process while CR comes 
up,
1. Feasibility Study
2. Impact Analysis (based on Tracability Matrix if exists)
3. Estimation (will be affected if the client have chances 
to provide further)
4. Implementation
5. Testing (should be careful about existing functionality)
6. Deployment and Deliverables

Hope you enjoing with my answer
Thanks,
Nagasundar Subramanian

Pre-sale
Req Analysis
Construction (Coding)
Testing
Deployement
Software Gurantee
Maintenance

SDLC is performed in two steps.
1. System Analysis and
2. System Design
System Analysis involves:
1. Problem Identification
2. Feasibility study and cost benefit analysis
3. System requirement analysis

System Design involves:
4. System design specifications and programming
5. System implementation, follow up and maintenance
6. Evaluation of the system

•The software concept - identifies and defines a need for 
the new system 

•A requirements analysis - analyzes the information needs 
of the end users 

•The architectural design - creates a blueprint for the 
design with the necessary specifications for the hardware, 
software, people and data resources 

•Coding and debugging - creates and programs the final 
system 

•System testing - evaluates the system's actual 
functionality in relation to expected or intended 
functionality.

first phase in SDLC is recognition of needs
second is feasibility study
third is analysis phase
fourth is designing phase
fifth is development ,implementation and testing phase
sixth phase is maintenance phase

The follwing are the phases of SDLC.
1. Definition of the problem - Identifying the requirement
2. User Requirement Study - Interview, JAD( Joint 
Application Development), Survey Method.
Outcome - Functional Specifications Document - High Level
3. Discussion and GAP Analysis - Submitting our level of 
understanding to the user and conduct suitable GAP analysis 
in understanding requirements.
Outcome - Detailed FS, Prototype, Use Cases, Flow charts, 
Logical Data Model and Process Model.
4. Feasibility Study and Cost Benefit Analysis
5. Sign-off and establish a protocol for Change Request.
6. Design - Functional and System Design
Outcome - Dataflow and process flow design with the 
suggested Design Methodology.
7. Development - Coding/programming the application.
8. Testing - Functional Testing (Black Box and White Box), 
Code Testing and User Acceptance Testing (Concurrent 
Testing (if multiple users are involved) and Regression 
Testing).
Outcome - Test Documents with error reporting at every 
stage.
9. Quality Management - Software quality team will check 
the system against established standards
Outcome - Certification
10. Implementation
11. Maintenance

SDLC has following 5 phases:-

1.Requirment ans Analysis (collect client requiremens and 
analyise it.)

2.Design phase(prepare design according to the 
requirements, Two type of desigs are develope,
 1.High level design(HLD) i.e is prepare for client
 2.Low level design(LLD) i.e used by developers.)

3.Coding phase(actul programing has been done)

4.Testing phase(the tester find the bugs)

5.Implementation and Maintinence(the product has released)

REQUIREMENT PHASE

DESIGN PHASE
    
    -High level design-> Implimentation & Techonology.
    -Low  level  design-> Requirement  Based Architecture . 

DEVELOPMENT ( CODING )  PHASE
    
    -Coding & Unit testing.

TESTING ( VERIFICATION ) PHASE
    
    -Integration testing.
    
    -System testing.
    
    -Acceptance testing.

MAINTAINANCE  PHASE
    -Evoluation.

1.feasibility study
2.requirements specification
3.design
4.coding
5.testing
6.implementation
7.maintenance

SDLC has following 6 phases:-

1.Requirment ans Analysis (collect client requiremens and 
analyise it.)

2.Design phase(prepare design according to the 
requirements, Two type of desigs are develope,
 1.High level design(HLD) i.e is prepare for client
 2.Low level design(LLD) i.e used by developers.)

3.Coding phase(actul programing has been done)

4.Testing phase(the tester find the bugs)

5.Implementation (implement a new list)

6.Maintanence(the product has released)

5 phases of SDLC

*Planning
*Analysis
*Design
*Implementation
   3 stages of implementation
    *Coding
    *Testing
    *Installation
*Maintenance - to insure the realibility

theee are mainly 4 phases are there
 1.planning
 2.analysi
 s.design
 4.imlimentation

SDLC means Software life Cycle model
it consists differnt phases like
1) initiation
2) Requirements
3) analysis
4) Design
5) codeing
6) implimentation

Following are the Different Software Development Life Cycle  
   (SDLC)Phases as follows :-
1  :- Communication - Requirement Analysis.
2  :- Planning - Planning related to all software development.
3  :- Modeling - Building a small prototype of product.
4  :- Construction - It again subdivided into two phases
 a :- Implementation - It involves actual Coding.   
 b :- Testing -All testing phases are done here.
5  :- Deployment - It involves deployment of the product(S/W).

planing 
analysis
testing
maintanance
degine

there are six phases of SDLC.
1.project identification and selection.
2.project initiaion and planning.
3.analysis.
4.design
  a)logical design
  b)physical design
5.implementation.
6.maintenance.

UAT

FOA - Field Operation Acceptance

uat-user aceeptance testing

There are various ways to record the record the 
requirements. Some of them capture it in Word, or Excel 
files. But there are tools to do that. For example DOORS 
from telelogic is a very popular tool used by many of them.