Why is Requirements Analysis necessary?

Studies reveal that inadequate attention to Software Requirements Analysis at the beginning of a project is the most common cause for critically vulnerable projects that often do not deliver even on the basic tasks for which they were designed. There are instances of corporations that have spent huge amounts on a software project where the end application eventually does not perform the tasks it was intended for.
Software companies are now investing time and resources into effective and streamlined Software Requirements Analysis Processes as a prerequisite to successful projects that align with the client’s business goals and meet the project’s requirement specifications.

Steps in the Requirements Analysis Process

I. Fix system boundaries
This initial step helps in identifying how the new application integrates with the business processes, how it fits into the larger picture and what its scope and limitations will be.
II. Identify the customer
In more recent times there has been a focus on identifying whom the ‘users’ or ‘customers’ of an application are. Referred to broadly as the ‘stake holders’, these indicate the group or groups of people who will be directly or indirectly impacted by the new application.
By defining in concrete terms who the intended user is, the Requirements Analyst knows in advance where he has to look for answers. The Requirements Elicitation Process should focus on the wish list of this defined group to arrive at a valid requirements list.
III. Requirements elicitation
Information is gathered from the multiple stakeholders identified. The Requirements Analyst draws out from each of these groups what their requirements from the application are and what they expect the application to accomplish.
Considering the multiple stakeholders involved, the list of requirements gathered in this manner could run into pages. The level of detail of the requirements list is based on the number and size of user groups, the degree of complexity of business processes and the size of the application.
a) Problems faced in Requirements Elicitation
· Ambiguous understanding of processes
· Inconsistency within a single process by multiple users
· Insufficient input from stakeholders
· Conflicting stakeholder interests
· Changes in requirements after project has begun
A Requirements Analyst has to interact closely with multiple work-groups, often with conflicting goals, to arrive at a bona fide requirements list. Strong communication and people skills along with sound programming knowledge are prerequisites for an expert Requirements Analyst.
b) Tools used in Requirements Elicitation
Traditional methods of Requirements Elicitation included stakeholder interviews and focus group studies. Other methods like flowcharting of business processes and the use of existing documentation like user manuals, organizational charts, process models and systems or process specifications, on-site analysis, interviews with end-users, market research and competitor analysis were also used extensively in Requirements Elicitation.
However current research in Software Requirements Analysis Process has thrown up modern tools that are better equipped to handle the complex and multi layered process of Requirements Elicitation. Some of the current Requirements Elicitation tools in use are:
· Prototypes
· Use cases
· Data flow diagrams
· Transition process diagrams
· User interfaces
IV. Requirements Analysis Process
Once all stakeholder requirements have been gathered, a structured analysis of these can be done after modeling the requirements. Some of the Software Requirements Analysis techniques used are requirements animation, automated reasoning, knowledge-based critiquing, consistency checking, analogical and case-based reasoning.
V. Requirements Specification
Requirements, once elicited, modeled and analyzed should be documented in clear, unambiguous terms. A written requirements document is critical so that its circulation is possible among all stakeholders including the client, user-groups, the development and testing teams. Current requirements engineering practices reveal that a well-designed, clearly documented Requirements Specification is vital and serves as a:
· Base for validating the stated requirements and resolving stakeholder conflicts, if any
· Contract between the client and development team
· Basis for systems design for the development team
· Bench-mark for project managers for planning project development lifecycle and goals
· Source for formulating test plans for QA and testing teams
· Resource for requirements management and requirements tracing
· Basis for evolving requirements over the project life span
Software requirements specification involves scoping the requirements so that it meets the customer’s vision. It is the result of collaboration between the end-user who is often not a technical expert, and a Technical/Systems Analyst, who is likely to approach the situation in technical terms.
The software requirements specification is a document that lists out stakeholders’ needs and communicates these to the technical community that will design and build the system. The challenge of a well-written requirements specification is to clearly communicate to both these groups and all the sub-groups within.
To overcome this, Requirements Specifications may be documented separately as
· User Requirements - written in clear, precise language with plain text and use cases, for the benefit of the customer and end-user
· System Requirements - expressed as a programming or mathematical model, addressing the Application Development Team and QA and Testing Team.
Requirements Specification serves as a starting point for software, hardware and database design. It describes the function (Functional and Non-Functional specifications) of the system, performance of the system and the operational and user-interface constraints that will govern system development.
VI. Requirements Management
Requirements Management is the comprehensive process that includes all aspects of software requirements analysis and additionally ensures verification, validation and traceability of requirements. Effective requirements management practices guarantee that all system requirements are stated unambiguously, that omissions and errors are corrected and that evolving specifications can be incorporated later in the project lifecycle.

Junior Telecom Officers-(JTO) - 2009

Download Application form

Application forms last date: 06.04.2009
Examination to be held on 21st June 2009 (Sunday)

Bharat Sanchar Nigam Ltd. [BSNL] will recruit about 3945 [subject to variation depending on the availability of vacancies] Junior Telecom. Officers (JTOs) through a competitive examination to be held on 21st June 2009 (Sunday) on All India basis.

Jobs Search Engine

Flow of G4Test

Login Page

Register yourself for apearing in recruitment process

Informatic Link

Click on link to Entering into the test interphase

Information About the test Composition

General Instructions:

You will be asked to complete a online form
Test centers do not have large waiting areas. Friends or relatives who accompany you to the test center will not be permitted to wait in the test center or contact you while you are taking the examination.
You will be required to write your signature before and after the test session and at any time you leave or enter the testing room.
You will be assigned a seat. Your picture will be taken and will be reproduced on your score report and at your testing station. Be sure the correct photograph is displayed on your assigned testing station.
You may not leave the test center during the test session and breaks.
You may not refer to or use any testing materials or aids at any time during the testing session or breaks. These include paper, pencils, beepers, pagers, pens, calculators, watch calculators, books, rulers, highlighter pens, stereos or radios with headphones, telephones/cell phones, electronic dictionaries, watch alarms, dictionaries, translators, and any electronic or photographic devices.
Scratch paper is provided you in test centre for rough work, which you have to handover to testing administrators before you leave the hall.
If at any time during the test you believe you have a problem with your computer or need the administrator for any reason, raise your hand.
The center administrator is authorized to dismiss you from a test session, or G4 Solutions may cancel your scores on following reasons
for attempting to take the test for someone else.
failing to provide acceptable identification
obtaining improper access to the test, a part of the test, or information about the test
using any prohibited aid in connection with the test
creating a disturbance
attempting to give or receive assistance, or otherwise communicate, in any form, with another person about the test, during the test administration
taking food or drink into the testing room
attempting to copy the test questions (in any format) from the testing room
attempting to take out the scratch paper from the testing room
leaving the testing room without permission
attempting to tamper with a computer
failing to follow any of the test administration regulations contained in this sheet or given by the test administrator, or specified in any test materials Failure to comply with an administrator’s directions can result in your test scores being canceled. If this should be necessary, no scores will be reported for this test.

In the web based test interface :

On the top of screen they see the name of the section
Followed by the question which is then followed by the options
They have to choose one of the option and then click on the next button to submit the question and view the next question
There is an list of all the questions below the previous and next button
They can randomly select any of the question from the list by clicking on the > (arrow) button in front of the that question

After giving the practice test, they may logged out automatically after 5 minutes and reach to the login page
They have to renter their user name and password to view the Real/ Main test.
In Real/ Main test of CapGemini there are two sections: Mathematical aptitude and Reasoning

Total number of questions are 50 to be solved in 60 minutes
Question no. 1 to 25: First section
Question no. 26 to 50: Second section
Both sections are compulsory
There is no negative marking
You can toggle between the sections
If you find any question difficult, you can leave it unanswered

BE students are required to select “CapGemini BE test” by clicking on execute link
MCA students are required select “CapGemini MCA test” by clicking on execute link

For the test participants

The test is computer based
Name of the test G4 Aptitude Testing for Recruitment (G4ATR) for CapGemini
Delivery Mode computer based
Multiple-answer choice questions
Automatically calculates the cumulative score for multiple answers
Enter your user name and password
Then you will be required to fill the online registration form
After completing the registration form click on submit
Upon clicking Submit button you will see the link “click here to start test”
By clicking on the link “click here to start test” you will view the practice test of 5 minutes which is having two links:

Info : click on it to see the information about the test
Execute : click on it to run the test

Instructions of G4Testing for CapGemini

What is Computer-Based G4testing for CapGemini:

A being administered computer format of the G4Testing for CapGemini. Test questions appear on the computer screen. Candidate will select -- by pointing and clicking a mouse -- the answer they believe is most appropriate in response to each question asked. It is not necessary to have previous computer experience. A 5 min practice test before the actual test gives you familiarization needed to take the test on computer, such as using a mouse, scrolling text up and down on the screen, and using the testing too.

G4 Aptitude Testing for Recruitment G4ATR) for CapGemini:

The G4ATR® for CapGemini is a standardized assessment test and checks the general aptitude. Each individual test that is administered contains the same format and areas of content. The test is comprised of two compulsory sections- quantitative, and reasoning. Each of these areas is measured using different types of questions that have specific instructions for each. It is important to recognize that the G4 ATR for CapGemini evaluates skills and abilities that develop over relatively long periods of time. The idea of computer based test is to bring transparency in term of testing, offer equal opportunity, stop malpractice and loop holes of paper based test.