Requirement Analysis

Published: Last Edited:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

Requirement Analysis

Requirement analysis is the process of understanding the user needs and what could be expected as the resulting application. The total description of the system how it works and or description of the properties and attributes. This analysis process could be divided into several types as user requirements, functional requirements, design requirements, performance requirements. The analysis gives chance to developer to understand the level of interaction between users, processes, specific requirements at the different level of within a company or outside the company. It also covers complex task of extracting and documenting for the requirement of all users, modelling and analyzing these requirements. Specialised and dedicated requirement analysis makes the work lot easier for the developer team to design and develop application because a proper documentation and the specific requirement analysis are keen area for the software success.

Why Requirement Analysis is necessary?

We have seen what Requirement Analysis is, but now we will look at the benefits of using it. This analysis process is prerequisite of successful projects, which aligned with the users, client's goals and project requirement specification. In further process it fixes the project boundaries to know how the new application going to integrate with the new business goals, how it could be helpful to its users, what are other scopes available for the user to be implement in new application which were not available before this.

Focuses on the customer or user needs, in broad area people who are directly or indirectly related with the new application, that's what called as performance parameter. This will answer all the question of the analyst to make a successful application for the users.

Requirement Specification

Requirement specification is a complete set of the behaviour of the application need to be developed. It includes functional requirements, number of user-software-hardware interaction of the user with the system, Non functional requirements such as design, quality, performance of the system.

Most of the functional requirements describe what the software will do and how it will expect to perform. It covers less the time period of the developers to achieve the desire goal and of course system development cost. How it could interact with system hardware, other programs and human users in real world defined by the functional requirements.

Benefit of Requirement Specification

The complete description of the function to be performed in the requirement will assist users to determine if the application meets their needs and or how the software could be modified to meet their needs. This specification forces developer to consider all of the requirements of the system before designing the application, to cut the cost and time for later to redesign, recoding and retesting. At early stages, a careful review of the specification makes easier to solve problem than later. The developing application should be realistically based on the estimated cost and the timeline provided by the customer. With good specification validation and verification plans could be more productive and also it makes easier to transfer new software application to new systems or new users.

In one statement, Requirement specification serves as a starting point for hardware software and database design, and describes the functional - Non functional specification of the system, performance, operational and user interface constraints.

Why do software project fails?

Research study says 50% of the new software project fails; there are some identified reasons for the failure. It believed that ‘Clear statement of requirements' is important, after User involvement and executive management support, for the success of a project with initially specified features and function and to be completed on time and on-budget. The project completed but over budget, over time estimated and allows to user fewer features and functions than originally specified.

Project success criteria could be divided in different ten steps.

  • User Involvement
  • Executive Management Support
  • Clear Statement of Requirements
  • Proper Planning
  • Realistic Expectations
  • Smaller Project Milestones
  • Competent Staff
  • Ownership
  • Clear Vision & Objectives
  • Hard-Working, Focused Staff

Among these ten steps first three are major factors to influence the success or failure of project. Most of the software development projects neglect requirement and analysis activities. Requirement model is the main communication between the company and developer team to share a common vision of the system solution. It will ensure the system meets all business needs and can be delivered on time within budget and have to have quality, flexibility and to accommodate with future system needs.

Hindsight Project begun in 1993 to translate and interpret the surviving text of western astrological tradition. As this project started in the research phase of project published a number of preliminary translations in three tracks originally classified by language: Greek, Latin and Hebrew.

Preliminary Translation been separated in Medieval track translation (Latin, Hebrew) and Hellenistic track translations (Greek).

Medieval track translation (Latin, Hebrew)

This astrology translation is an extremely detailed and advanced on the subject of solar returns. This work is so full of detail the analysis took about a year. Apart from its great intrinsic interest this work was important for two addition reasons. First, precious little remains of Hellenistic solar return doctrine although it was clearly considered to be important. Second, it is representative of important Arabian material that did not make it into the Medieval Latin tradition until the 16th therefore; this doctrine scarcely had time to be assimilated to the tradition before astrology nearly dropped out of the picture in the late 17th century.

Hellenistic track translations (Greek)

This translation includes method for investigating life expectancy based on study of the Moon to other planets and a procedure for determining a succession of planets that have primary authority over the native's successes and failures in all areas of life. An important timing procedure that derives directly from the earliest stratum of Hellenistic astrology.

The Hindsight project was founded for the purpose of translating the texts of the Western astrological tradition into English and making that available to the astrology community. As this project was something of a gamble, developers found anything of capital importance for astrologers by undertaking to translate and study the original source texts of western astrology. In every other case where Greek writings of a classical or Hellenistic periods had been dismissed or as evidence of the decline of classical thought, study had subsequently reversed that premature verdict.

The project model been taken as a programme of the late Renaissance to restore the lost art of ancient algebra and ended up founding modern mathematics. In ancient time algebra did not have the countenance , was regarded by some of the occult disciplines and occasionally even tarred with the black art.

Finally by the experience as the example of the mathematical restorers, the immersion in past though was an excellent way of gaining some distance and clarity about modern thinking in a given discipline, the study of foreign language is acknowledged to enhance the understanding of one's native language.

The Hindsight project took about more than twelve years to finish, it is a great value material for the modern astrologers and philosophy students. The developers research and hard work been paid off.

It have been discovered that there was in fact a coherent system of astrological practice during the Hellenistic period that did not reveal itself to the few classicists and historians of science who have looked into these texts. The system been restored in its original form, this practical system was motivated by a set of theoretical assumptions that has important and independent implications for logic, epistemology, and metaphysics-hard as that may be to accept for those to whom the subject of astrology is automatically an occasion for ridicule.

After reading this all material I have come to the conclusion that The Project HindSight is a quite a big project where developer are researcher, data collector and the base of the project, But in the beginning they have no idea from where to start but they have a vision to develop a astrology software program which can tell a person future. During the project they came across to different astrology methods and some mathematic calculations. Some of the methods been written to different language and it was essential to convert to English language for the broad understanding. Some of the translation took over a year and till that time research about the subject continuous to fulfil the system requirement. Some of the research is still going on to make the software more accurate and efficient. Well in my opinion this project does not have result yet the research and modernize of the software still being worked.

As we discussed about the Requirement analysis and specification earlier was not directly related to this topic, because some huge project like this where developing team have not full information and specified requirements always takes much longer time than expected. And during this project many changes had been done by learning experience.