SlideShare ist ein Scribd-Unternehmen logo
1 von 6
Downloaden Sie, um offline zu lesen
International Journal of Engineering Research & Technology (IJERT)
                                                                                                                                    ISSN: 2278-0181
                                                                                                                           Vol. 1 Issue 5, July - 2012




 QUANTIFICATION OF FUNCTIONAL REQUIREMENTS IN
   SOFTWARE SYSTEM ENGINEERING USING LPP
                                                M.Karthika,
                                          X.Joshphin Jasaline Anitha
                                              Dr.K.Alagarsamy
    Assistant Professor ,MCA DepartmentNMSS Vellaichamy Nadar College Nagamalai,Madurai, Tami Nadu, India
    Assistant Professor ,MCA DepartmentNMSS Vellaichamy Nadar College, Nagamalai,Madurai, Tami Nadu, India

        Associate professor,Computer CentreMadurai Kamaraj University, Nagamalai,Madurai, Tami Nadu, India




                      ABSTRACT                                          that best satisfies that need. It is a generic problem-solving
Software systems developed now-a- days are by and large                 process that applies to the overall technical management of a
more complicated than the existing software. There are                  system development project. This process provides the
certain foundational activities for a system development like           mechanism for identifying and evolving a system’s product
the objective of the system, operational requirements, role of          and process definitions. System engineering involves five
hardware and software, the people working in it, database               functions: Problem definition, Solution analysis, Process
used and the procedures. On understanding the foundational              planning, Process control and Product evaluation [7].
activities based on the System Engineering principle to                 System engineering provides the baseline for all project
transform an operational need into more descriptive and will            development, as well as a mechanism for defining the solution
lead to build a right and good product with customer                    space. The solution space describes the product at the highest
satisfaction. The operational requirements of software system           level – before the system requirements are partitioned into the
engineering have been classified already .In this paper, the            hardware and software subsystems.
functional requirements classified is common for all the
software system developed. Also, it brought out the important           The developed software has become very larger and more
role of functional requirements which can effectively be uses           complex than the existing software. The complexity has been
to elicit information from the customers more precisely and             increased in variety of phases in the software development life
accurately through LPP approach. The LPP assigns,                       cycle. The understanding of the problem must enforce the
identifies, classifies and optimize the functional requirements         below mentioned in system engineering [8].
which will provide an insight into the system architecture,
                                                                                  Requirement analysis
also helps to communicate the operational and behavioral
                                                                                  Design
characteristics of the new system.
                                                                                  Implementation
Keywords                                                                          Verification & Validation
                                                                                  Testing
System Engineering, Software System Engineering,
Functional requirements, product, Evaluation criteria,LPP
                                                                        System Engineering focuses on variety of elements,
1. INTRODUCTION                                                         analyzing, designing and organizing those elements into a
                                                                        system that can become a product, a service or a technology
As large systems functions and solutions are dependent on               for the transformations or control. Software system
software, System Engineering approach to the development of             engineering manages the technical function of the system
software will help to avoid the problems associated with the            products, which produces set of documents. This is a technical
software crisis. These crisis are mainly on the project                 process which converts the analytical process into an
schedule, cost of estimation, customer satisfaction. A                  operational process such as [2],
Software product developed may face challenging facts, risks,
and issues in managerial aspects such as logistics, lack of co-                   Define the problem
ordination between the teams developing the product as well                       Identify feasible alternatives
as the work process. The need to identify and manipulate the                      Select the evaluation criteria
properties of a software system leads to the use of software                      Applying modeling techniques
system engineering. [1]                                                           Generate input data
 A system is a group of co-related objects that allows a                          Manipulate the model
common goal to be accomplished. In computer systems, these
elements include hardware, software, people, facilities, and            This paper categorizes and concentrates only on the functional
processes.                                                              requirements in the software requirement stage in accordance
System engineering is the practical application of scientific,          with the principles of system engineering and its tools.
engineering, and management skills necessary to transform an
operational need into a description of a system configuration




                                                             www.ijert.org                                                                         1
International Journal of Engineering Research & Technology (IJERT)
                                                                                                                                          ISSN: 2278-0181
                                                                                                                                 Vol. 1 Issue 5, July - 2012




2. SOFTWARE SYSTEM                                                         software systems that provides a powerful tool for process and
                                                                           product management. The software system is larger and has
    ENGINEERING                                                            high complexity in using it. This will attribute towards the
                                                                           growth in hardware performance as well as the software
The application of system engineering principle to the                     performance by having reduced software system size which
development of a computer software system prepares                         makes the software more complex. The goal of SwSE is to
activities, tasks and various set of procedures that is called as          reduce the complexity through several stages of verification
software system engineering (SwSE).This SwSE can be                        and validation.
specifically applied in the development of large complex

                                                   Software System Engineering




            Requirement            Design               Planning                Managing         Verification, Validation,
            Analysis                                                                             Testing

           Fig .1. Phases in Software System engineering
                                                                           activities to determine that they are following the technical
Software system Engineering manages the technical function
                                                                           and managerial plans, specifications, standards, and
of the system products which produces the documents for
                                                                           procedures. V&V. evaluate the interim and final product of
reference. Evaluation criteria, a series of steps or an iterative
                                                                           software engineering.
process using genetic algorithms can give this documentation
reference.                                                                 The user satisfaction must meet out through the system
                                                                           engineers. The success of software development process and
To achieve a successful process, planning is necessary.
                                                                           the system life cycles undergoes much revaluation process to
Planning tells us the goals in a project the objectives,
                                                                           redefine the functional requirements.
strategies, polices, plans, and procedure. It tells us in advance
what, how, when and who will do the process. To plan a                     2.1 Requirement Analysis
software engineering project we need SWSE management
                                                                           The first step in any software development activity is to
activities that lead in selecting a course of action from
                                                                           determine and document the system-level requirements in
alternative possibilities and defining a program for completing
                                                                           either a system requirements specification (SRS) or a software
those actions.
                                                                           requirements specification or both. Software requirements
The collection of management activities that used to ensure                include capabilities that a user needs to solve a problem or
that the project goes according to the plan is known as process            achieve an objective as well as capabilities that a system or
control. The performance and results against plans, notes                  component needs to satisfy a contract, standard, or other
deviations measured using process control. It takes corrective             formally imposed document. Software requirements analysis
actions to ensure conformance between plans and actual                     begins after system engineering has defined the acquirer and
results. Process control gives us a feedback to the system for             user system requirements. Its functions include identification
how well the project is going. In system, engineering V&V is               of all – or as many as possible – software system
a continuous process of-monitoring system engineering,                     requirements, and its conclusion marks the established
SwSE, software engineering, and project management                         requirements baseline, sometimes called the allocated baseline
                                                                           [3].

                                         Requirement Analysis




  Functional Requirement                                                        Non-Functional
  Analysis                                                                      Requirement Analysis



   User Interface                                                               Performance
   Transaction Performance                                                      External Interface
   Auditing                                                                     Design Constraints
                                                                                Quality Attributes
   Authentication


Fig.2. Software Requirement Analysis                                               We can categorize software requirements as shown in
                                                                                   Fig.2.Functional requirements specify functions that a
   Authentication




                                                                www.ijert.org                                                                            2
International Journal of Engineering Research & Technology (IJERT)
                                                                                                                                    ISSN: 2278-0181
                                                                                                                           Vol. 1 Issue 5, July - 2012




system or system component must be capable of                                                o     Identification
performing.                                                                                  o     Reaction
Non-Functional requirements, which include the                                               o     Behavior
Performance requirements, specify performance
                                                                                        Transaction based performance
characteristics that a system or system component must
possess such as speed, accuracy, and frequency. External                                     o     Identification
interface requirements specify hardware, software, or
database elements with which a system or component                                           o     Reaction
must interface, or set forth constraints on formats,                                         o     Behavior
timing, or other factors caused by such an interface.
Design constraints affect or constrain the design of a                                  Auditing
software system or software system component, for
                                                                                             o     Functions
example, language requirements, physical hardware
requirements, software development standards, and                                            o     Limitations
software quality assurance standards. Quality attributes
specify the degree to which software possesses attributes                               Authentication
that affect quality, such as correctness, reliability,                                       o     Members
maintainability, and portability.
                                                                                             o     Managers
                                                                                             o     Administrators.
3. FUNCTIONAL REQUIREMENTS

In software system engineering, a functional requirement
defines a function of a software system or its
component. A function is described as a set of inputs,
the behavior, and outputs. Functional requirements may
be calculations, technical details, data manipulation and
processing and other specific functionality that define
what a system is supposed to accomplish. Behavioral
requirements describing all the cases where the system                        3.1 Model system for functional
uses the functional requirements are captured in use
cases. Functional requirements are supported by non-                              Requirements:
functional requirements, which impose constraints on                          The representation for the requirement starts from the
the design or implementation, such as performance                             world view to the design view. This may be a top down
requirements, security, or reliability. Acceptable systems                    or bottom up approach. A system should be modeled,
must satisfy all the mandatory requirements. [12]                             which has an element and also plays a vital role in the
                                                                              development process [9] [10].
Functional requirements are based on the following four
classical members have been depicted in Fig .3 as,                            Now the modeled developed is top down approach, so it
                                                                              starts form
                                                                                        Defining the processes
                                                                                        Represent the behavior of the processes
         User Interface                                                                 assumptions on which the behavior is based.
                                                                                        Explicitly define the exogenous               end
                              Functional                                                endogenous input to the model.
                              Requirements                                              Represent all the links.
           Auditing                          Authentication                    In constructing a model, the restraining factors such as
                                                                              assumptions, simplifications, limitations and constraints
                                                                              must be considered.
                                                                              Representing the requirements in World view (WV) as,

                                                                                        WV          D1 , D2 , D3 ..., Dn
Fig.3. Classification of Functional Requirements.
                                                                                        Di       D1 , D2 , D3 ..., Dn
                                                                              Di are the Set of domains either systems / subsystems.
                                                                              Representing the requirement as Domain view (DV),

                                                                                        DV          E1 , E2 , E3 ,...Em
          Retrieving input from the user




                                                              www.ijert.org                                                                        3
International Journal of Engineering Research & Technology (IJERT)
                                                                                                                                           ISSN: 2278-0181
                                                                                                                                  Vol. 1 Issue 5, July - 2012




           Ej     E1 , E2 , E3 ,..., Em                                              engineering plays in complex projects. An
                                                                                     Heuristic approach which will optimize the
Ej are the set of elements which satisfies the objective or                          complex problems through various techniques.
the goal of accomplished tasks.
                                                                                     These techniques and methods leads to feasible
Representing the Elemental view (EV) as,                                             solution through LPPs. There are various methods
                                                                                     through which optimal solution can be obtained.
           EV       C1 , C2 , C3 ,...Ck
                                                                                     Like, Least cost method, North west corner rule,
          Ck      C1 , C2 , C3 ,..., Ck                                              Traveling sales person problem[19].

Ck are the set of technical components that achieves the
necessary function of an element [3].
These assumptions shown in Fig.4, of world, domain,
elementary and components of the can be evaluated via
a genetic algorithmic approach.




                                                 World View( Requirement analysis)




                       Domain View 1( Functional)                          Domain View 2(Non-
                                                                           Functional)




     Elementary View 1(Retreiving                 Elementary View2 Transaction                      Elementary View 3 Auditing
     Input from the user)                         Performance




                                                                                         Operations research, briefly, is concerned with
                                                                                     the optimization of a process under multiple
                                Detailed view1                  Detailed view2           Detailed view3       …
                                                                                     constraints. This paper takes into consideration the
                                Identification                  Reaction                 Behavior
                                                                                     optimization technique – assignment problem,
                                                                                     which helps to have minimal time period and can
                                                                                     achieve an approximate solution which is
                                                                                     responsible for preparing a decision making
                                                                                     system.
Fig. 4. A Model Representation - Functional
requirements.                                                                        This decision can be applied to complex programs.
                                                                                     It is taken into consideration that constraints at
4. EVALUATION OF REQUIREMENTS                                                        various levels.
THROUGH AN LPP                                                                       The Assignment Problem
                                                                                         The simple assignment problem which helps to
4.1 Operation Research In System                                                     optimize and reduce the cost of the product. On the
Engineering                                                                          basis of the output, the product will be identified to
                                                                                     be an optimized. This will help the software
    Operations    research   supports    systems
                                                                                     organization to identify the minimum cost of the
engineering. The tools of operations research are
                                                                                     product and cost taken to complete the process.
used in systems analysis, decision making, and
trade studies. Highlights the role systems




                                                                  www.ijert.org                                                                           4
International Journal of Engineering Research & Technology (IJERT)
                                                                                                                              ISSN: 2278-0181
                                                                                                                     Vol. 1 Issue 5, July - 2012




    An assignment problem is a special type of                          row, and is the assignment that minimizes risk of
linear programming problem where the objective is                       the requirement analysis.
to minimize the cost or time of completing a
number of jobs by a number of persons [20].



A typical assignment problem, presented in the
classic manner, is shown in Fig. 12. Here there are
five customers to be assigned to five requirements.
The numbers in the matrix indicate the cost of
doing each requirement analysis with each module.
project with costs of M are disallowed                                  Figure 7. Solution to the requirement optimization
assignments. The problem is to find the minimum                                              Problem
time to matching the requirements to products.
                                                                        so, in searching a large state-space, multi-modal
                                                                        state-space, or n-dimensional surface, a genetic
                                                                        algorithm may offer significant benefits over more
                                                                        typical search of Optimization Techniques. (linear
                                                                        programming, heuristic, depth-first, breath-first,
                                                                        and praxis.)



                                                                        5. CONCLUSION
   Figure.5. Matrix model of the requirements.                          Software System Engineering performs a variety
                                                                        of functions at various stages in the product
The network model is in Fig. 6. It is very similar to                   development life cycle. Software Requirement
the transportation model except the external flows                      Analysis is a phase in which reevaluation has to be
are all +1 or -1. The only relevant parameter for                       started. Requirements are classified into functional
the assignment model is arc cost (not shown in the                      and non-functional requirements relevant to the
figure for clarity) ; all other parameters should be                    product or process developed. The functional
set to default values. The assignment network also                      requirements categorized as, user interface,
has the bipartite structure.                                            transaction     performance,       auditing      and
                                                                        authentication were done in accordance with their
                                                                        functions. The basic representation which is
                                                                        relevant to software system engineering such as
                                                                        world, domain, elementary and component view
                                                                        were discussed. The views noted have been
                                                                        approached from top - down. This paper focuses
                                                                        on using the LPP to have an iterative process of
                                                                        identifying and refining the requirements by a method of
                                                                        reevaluation. A series of repeated steps using the tool
                                                                        will help us to elicit all the requirements to develop the
                                                                        design phase successfully.

                                                                        6. REFERENCES


                                                                        [1] A.Terry Bahill, Clark Biggs, “ The Systems
                                                                            Engineering started in the middle process: a
                                                                            consensus of system Engineers and project
                                                                            Mangers, 2001, John Wiley & sons, Inc.syst
                                                                            Eng:156 – 157.
  Figure 6. Network model of the requirements.
                                                                        [2] Eushiuan Tran ,           “      Requirements         &
                                                                            Specification”
The solution to the assignment problem as shown
in Fig. 7 has a total flow of 1 in every column and                     [3] Quantifying Software Reliability Readiness Astana,
                                                                            A.; Olivieri, J. ; Alcatel - Lucent, Westford, MA,
                                                                            USA




                                                        www.ijert.org                                                                        5
International Journal of Engineering Research & Technology (IJERT)
                                                                                                                            ISSN: 2278-0181
                                                                                                                   Vol. 1 Issue 5, July - 2012




[4] Software Engineering a Practioner’s      Approach,
    sixth Edition, Roger S.Pressman.
[5] Software Engineering Theory and Practice,
    Fourth Edition, Shari Lawerence Fleeger, Joanne M.
    Atlee.
[6] A. J. Chipperfield and P. J. Fleming, the MATLAB
    Genetic Algorithm Toolbox.
[7] Richard H.Thayer, “Software System Engineering: A
    Tutorial”IEEE 2002, pp 68-73.
[8] Eric C.Honour, “ Understanding the Value of
    System Engineering”
[9] “Introduction to Systems Engineering”
[10] Linda    Westfall,  “Software   Requirements
     Engineering: What, Why, Who, When, and How”,
     2005-2006.
[11] Dr.Judith Dahmann, “Importance of systems
     engineering in Early Acquisition”.
[12] www.ofnisystems.com/Validation/Functional_Req
     uirements.htm
[13] Terry Bahill, “The Eight System Engineering
     Documents”, 2001-2009.
[14] A.Terry Bahill, Frank F. Dean, “What is system
     engineering? A consensus of senior system
     Engineers”, Jan 15, 2009.
[15] Dr. Laurie Williams, “ A (Partial) Introduction to
     Software Engineering Practices and Methods”,
     NCSU CSC326 Course Pack, 2008-2009
     (Fifth) Editions.
[16] Prof. Dr. Oscar Nierstrasz, Dr. St´ephane
     DucasseMichele Lanza, “Recovering the Evolution
     of Object Oriented SoftwareSystems Using a
     Flexible Query Engine”, June 2001.
[17] Ruth Malan and Dana Bredemeyer “Functional
     Requirements and Use Cases”.
[18] http://media.wiley.com/product_data/excerpt/96/
     07695119/0769511996.pdf.
[19] http://businessmanagementcourses.org/Lesson19
     AssignmentProblem.pdf
[20] Operations Research: An Introduction (7th Edition)
     Hamdy A. Taha
[21] Quantifying Software Reliability Readiness
     Asthana, A.; Olivieri, J.;
     Alcatel-Lucent, Westford, MA, USA




                                                          www.ijert.org                                                                    6

Más contenido relacionado

Was ist angesagt?

Ian Sommerville, Software Engineering, 9th Edition Ch2
Ian Sommerville,  Software Engineering, 9th Edition Ch2Ian Sommerville,  Software Engineering, 9th Edition Ch2
Ian Sommerville, Software Engineering, 9th Edition Ch2Mohammed Romi
 
Model-Based Performance Prediction in Software Development: A Survey
Model-Based Performance Prediction in Software Development: A SurveyModel-Based Performance Prediction in Software Development: A Survey
Model-Based Performance Prediction in Software Development: A SurveyMr. Chanuwan
 
Enhancing the flexibility to the design of selangkah system
Enhancing the flexibility to the design of selangkah systemEnhancing the flexibility to the design of selangkah system
Enhancing the flexibility to the design of selangkah systemizzatuitm
 
Literature Review
Literature ReviewLiterature Review
Literature Reviewizzatuitm
 
Performance testing based on time complexity analysis for embedded software
Performance testing based on time complexity analysis for embedded softwarePerformance testing based on time complexity analysis for embedded software
Performance testing based on time complexity analysis for embedded softwareMr. Chanuwan
 
Systems engineering for project managers - what you need to know
Systems engineering for project managers - what you need to knowSystems engineering for project managers - what you need to know
Systems engineering for project managers - what you need to knowAssociation for Project Management
 
Software Quality
Software QualitySoftware Quality
Software Qualitysjavaad
 
Software Engineering Past Papers (Short Questions)
Software Engineering Past Papers (Short Questions)Software Engineering Past Papers (Short Questions)
Software Engineering Past Papers (Short Questions)MuhammadTalha436
 
Software re engineering
Software re engineeringSoftware re engineering
Software re engineeringdeshpandeamrut
 
Se solns 9th edition
Se solns 9th editionSe solns 9th edition
Se solns 9th editionrajabaidyo
 
Ch2-Software Engineering 9
Ch2-Software Engineering 9Ch2-Software Engineering 9
Ch2-Software Engineering 9Ian Sommerville
 
Se lect12 btech
Se lect12 btechSe lect12 btech
Se lect12 btechIIITA
 
Se lect13 btech
Se lect13 btechSe lect13 btech
Se lect13 btechIIITA
 
Intoduction to software engineering part 1
Intoduction to software engineering part 1Intoduction to software engineering part 1
Intoduction to software engineering part 1Rupesh Vaishnav
 

Was ist angesagt? (20)

Ian Sommerville, Software Engineering, 9th Edition Ch2
Ian Sommerville,  Software Engineering, 9th Edition Ch2Ian Sommerville,  Software Engineering, 9th Edition Ch2
Ian Sommerville, Software Engineering, 9th Edition Ch2
 
Model-Based Performance Prediction in Software Development: A Survey
Model-Based Performance Prediction in Software Development: A SurveyModel-Based Performance Prediction in Software Development: A Survey
Model-Based Performance Prediction in Software Development: A Survey
 
Software engg unit 2
Software engg unit 2 Software engg unit 2
Software engg unit 2
 
Enhancing the flexibility to the design of selangkah system
Enhancing the flexibility to the design of selangkah systemEnhancing the flexibility to the design of selangkah system
Enhancing the flexibility to the design of selangkah system
 
Literature Review
Literature ReviewLiterature Review
Literature Review
 
Software engg unit 4
Software engg unit 4 Software engg unit 4
Software engg unit 4
 
Performance testing based on time complexity analysis for embedded software
Performance testing based on time complexity analysis for embedded softwarePerformance testing based on time complexity analysis for embedded software
Performance testing based on time complexity analysis for embedded software
 
Systems engineering for project managers - what you need to know
Systems engineering for project managers - what you need to knowSystems engineering for project managers - what you need to know
Systems engineering for project managers - what you need to know
 
Software Quality
Software QualitySoftware Quality
Software Quality
 
Ch7
Ch7Ch7
Ch7
 
Software Engineering Past Papers (Short Questions)
Software Engineering Past Papers (Short Questions)Software Engineering Past Papers (Short Questions)
Software Engineering Past Papers (Short Questions)
 
Ch19 systems engineering
Ch19 systems engineeringCh19 systems engineering
Ch19 systems engineering
 
Software re engineering
Software re engineeringSoftware re engineering
Software re engineering
 
software re-engineering
software re-engineeringsoftware re-engineering
software re-engineering
 
Se solns 9th edition
Se solns 9th editionSe solns 9th edition
Se solns 9th edition
 
factors
 factors factors
factors
 
Ch2-Software Engineering 9
Ch2-Software Engineering 9Ch2-Software Engineering 9
Ch2-Software Engineering 9
 
Se lect12 btech
Se lect12 btechSe lect12 btech
Se lect12 btech
 
Se lect13 btech
Se lect13 btechSe lect13 btech
Se lect13 btech
 
Intoduction to software engineering part 1
Intoduction to software engineering part 1Intoduction to software engineering part 1
Intoduction to software engineering part 1
 

Andere mochten auch

Andere mochten auch (9)

Difference between c and c
Difference between c and cDifference between c and c
Difference between c and c
 
Sermon 10 10_10pm
Sermon 10 10_10pmSermon 10 10_10pm
Sermon 10 10_10pm
 
Mighty warrior class 8 25-10
Mighty warrior class 8 25-10Mighty warrior class 8 25-10
Mighty warrior class 8 25-10
 
Versioning
VersioningVersioning
Versioning
 
Oct conference1
Oct conference1Oct conference1
Oct conference1
 
Sermon 10 10_10pm
Sermon 10 10_10pmSermon 10 10_10pm
Sermon 10 10_10pm
 
Mighty warrior class 8 25-10
Mighty warrior class 8 25-10Mighty warrior class 8 25-10
Mighty warrior class 8 25-10
 
Files
FilesFiles
Files
 
Cprogramcontrolifelseselection3
Cprogramcontrolifelseselection3Cprogramcontrolifelseselection3
Cprogramcontrolifelseselection3
 

Ähnlich wie functional requirements using LPP

Software engineering
Software engineeringSoftware engineering
Software engineeringh2eEdgar
 
ccs356-software-engineering-notes.pdf
ccs356-software-engineering-notes.pdfccs356-software-engineering-notes.pdf
ccs356-software-engineering-notes.pdfVijayakumarKadumbadi
 
Software Engineering UPTU
Software Engineering UPTUSoftware Engineering UPTU
Software Engineering UPTURishi Shukla
 
Fostering MBSE in Engineering Culture
Fostering MBSE in Engineering CultureFostering MBSE in Engineering Culture
Fostering MBSE in Engineering CultureObeo
 
A system for performance evaluation of embedded software
A system for performance evaluation of embedded softwareA system for performance evaluation of embedded software
A system for performance evaluation of embedded softwareMr. Chanuwan
 
Asystemforperformanceevaluationofembeddedsoftware 100813001230-phpapp02
Asystemforperformanceevaluationofembeddedsoftware 100813001230-phpapp02Asystemforperformanceevaluationofembeddedsoftware 100813001230-phpapp02
Asystemforperformanceevaluationofembeddedsoftware 100813001230-phpapp02NNfamily
 
software engineering
software engineeringsoftware engineering
software engineeringsubhakirthi
 
want to contact me login to www.stqa.org
want to contact me login to www.stqa.orgwant to contact me login to www.stqa.org
want to contact me login to www.stqa.orgnazeer pasha
 
Software engineering : Layered Architecture
Software engineering : Layered ArchitectureSoftware engineering : Layered Architecture
Software engineering : Layered ArchitectureMuhammed Afsal Villan
 
Lecture - 7-10.pptx
Lecture - 7-10.pptxLecture - 7-10.pptx
Lecture - 7-10.pptxFarHana74914
 
Introduction to Software Engineering
Introduction to Software EngineeringIntroduction to Software Engineering
Introduction to Software EngineeringZahoor Khan
 
Software engineering introduction
Software engineering   introductionSoftware engineering   introduction
Software engineering introductionDr. Loganathan R
 
Performancetestingbasedontimecomplexityanalysisforembeddedsoftware 1008150404...
Performancetestingbasedontimecomplexityanalysisforembeddedsoftware 1008150404...Performancetestingbasedontimecomplexityanalysisforembeddedsoftware 1008150404...
Performancetestingbasedontimecomplexityanalysisforembeddedsoftware 1008150404...NNfamily
 
Chapter_01.ppt
Chapter_01.pptChapter_01.ppt
Chapter_01.pptMSahibKhan
 
مناهج التعليم وصناعة البرمجيات
مناهج التعليم وصناعة البرمجياتمناهج التعليم وصناعة البرمجيات
مناهج التعليم وصناعة البرمجياتEiman Idris
 

Ähnlich wie functional requirements using LPP (20)

Software engineering
Software engineeringSoftware engineering
Software engineering
 
ccs356-software-engineering-notes.pdf
ccs356-software-engineering-notes.pdfccs356-software-engineering-notes.pdf
ccs356-software-engineering-notes.pdf
 
Software Engineering UPTU
Software Engineering UPTUSoftware Engineering UPTU
Software Engineering UPTU
 
Fostering MBSE in Engineering Culture
Fostering MBSE in Engineering CultureFostering MBSE in Engineering Culture
Fostering MBSE in Engineering Culture
 
A system for performance evaluation of embedded software
A system for performance evaluation of embedded softwareA system for performance evaluation of embedded software
A system for performance evaluation of embedded software
 
Asystemforperformanceevaluationofembeddedsoftware 100813001230-phpapp02
Asystemforperformanceevaluationofembeddedsoftware 100813001230-phpapp02Asystemforperformanceevaluationofembeddedsoftware 100813001230-phpapp02
Asystemforperformanceevaluationofembeddedsoftware 100813001230-phpapp02
 
Seii unit4 software_process
Seii unit4 software_processSeii unit4 software_process
Seii unit4 software_process
 
Chapter1
Chapter1Chapter1
Chapter1
 
software engineering
software engineeringsoftware engineering
software engineering
 
want to contact me login to www.stqa.org
want to contact me login to www.stqa.orgwant to contact me login to www.stqa.org
want to contact me login to www.stqa.org
 
Software engineering : Layered Architecture
Software engineering : Layered ArchitectureSoftware engineering : Layered Architecture
Software engineering : Layered Architecture
 
3 management
3 management3 management
3 management
 
Lecture - 7-10.pptx
Lecture - 7-10.pptxLecture - 7-10.pptx
Lecture - 7-10.pptx
 
Introduction to Software Engineering
Introduction to Software EngineeringIntroduction to Software Engineering
Introduction to Software Engineering
 
Software engineering introduction
Software engineering   introductionSoftware engineering   introduction
Software engineering introduction
 
Lecture 1 SE.pptx
Lecture 1 SE.pptxLecture 1 SE.pptx
Lecture 1 SE.pptx
 
Performancetestingbasedontimecomplexityanalysisforembeddedsoftware 1008150404...
Performancetestingbasedontimecomplexityanalysisforembeddedsoftware 1008150404...Performancetestingbasedontimecomplexityanalysisforembeddedsoftware 1008150404...
Performancetestingbasedontimecomplexityanalysisforembeddedsoftware 1008150404...
 
Chapter_01.ppt
Chapter_01.pptChapter_01.ppt
Chapter_01.ppt
 
Software engineer
Software engineerSoftware engineer
Software engineer
 
مناهج التعليم وصناعة البرمجيات
مناهج التعليم وصناعة البرمجياتمناهج التعليم وصناعة البرمجيات
مناهج التعليم وصناعة البرمجيات
 

functional requirements using LPP

  • 1. International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 1 Issue 5, July - 2012 QUANTIFICATION OF FUNCTIONAL REQUIREMENTS IN SOFTWARE SYSTEM ENGINEERING USING LPP M.Karthika, X.Joshphin Jasaline Anitha Dr.K.Alagarsamy Assistant Professor ,MCA DepartmentNMSS Vellaichamy Nadar College Nagamalai,Madurai, Tami Nadu, India Assistant Professor ,MCA DepartmentNMSS Vellaichamy Nadar College, Nagamalai,Madurai, Tami Nadu, India Associate professor,Computer CentreMadurai Kamaraj University, Nagamalai,Madurai, Tami Nadu, India ABSTRACT that best satisfies that need. It is a generic problem-solving Software systems developed now-a- days are by and large process that applies to the overall technical management of a more complicated than the existing software. There are system development project. This process provides the certain foundational activities for a system development like mechanism for identifying and evolving a system’s product the objective of the system, operational requirements, role of and process definitions. System engineering involves five hardware and software, the people working in it, database functions: Problem definition, Solution analysis, Process used and the procedures. On understanding the foundational planning, Process control and Product evaluation [7]. activities based on the System Engineering principle to System engineering provides the baseline for all project transform an operational need into more descriptive and will development, as well as a mechanism for defining the solution lead to build a right and good product with customer space. The solution space describes the product at the highest satisfaction. The operational requirements of software system level – before the system requirements are partitioned into the engineering have been classified already .In this paper, the hardware and software subsystems. functional requirements classified is common for all the software system developed. Also, it brought out the important The developed software has become very larger and more role of functional requirements which can effectively be uses complex than the existing software. The complexity has been to elicit information from the customers more precisely and increased in variety of phases in the software development life accurately through LPP approach. The LPP assigns, cycle. The understanding of the problem must enforce the identifies, classifies and optimize the functional requirements below mentioned in system engineering [8]. which will provide an insight into the system architecture, Requirement analysis also helps to communicate the operational and behavioral Design characteristics of the new system. Implementation Keywords Verification & Validation Testing System Engineering, Software System Engineering, Functional requirements, product, Evaluation criteria,LPP System Engineering focuses on variety of elements, 1. INTRODUCTION analyzing, designing and organizing those elements into a system that can become a product, a service or a technology As large systems functions and solutions are dependent on for the transformations or control. Software system software, System Engineering approach to the development of engineering manages the technical function of the system software will help to avoid the problems associated with the products, which produces set of documents. This is a technical software crisis. These crisis are mainly on the project process which converts the analytical process into an schedule, cost of estimation, customer satisfaction. A operational process such as [2], Software product developed may face challenging facts, risks, and issues in managerial aspects such as logistics, lack of co- Define the problem ordination between the teams developing the product as well Identify feasible alternatives as the work process. The need to identify and manipulate the Select the evaluation criteria properties of a software system leads to the use of software Applying modeling techniques system engineering. [1] Generate input data A system is a group of co-related objects that allows a Manipulate the model common goal to be accomplished. In computer systems, these elements include hardware, software, people, facilities, and This paper categorizes and concentrates only on the functional processes. requirements in the software requirement stage in accordance System engineering is the practical application of scientific, with the principles of system engineering and its tools. engineering, and management skills necessary to transform an operational need into a description of a system configuration www.ijert.org 1
  • 2. International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 1 Issue 5, July - 2012 2. SOFTWARE SYSTEM software systems that provides a powerful tool for process and product management. The software system is larger and has ENGINEERING high complexity in using it. This will attribute towards the growth in hardware performance as well as the software The application of system engineering principle to the performance by having reduced software system size which development of a computer software system prepares makes the software more complex. The goal of SwSE is to activities, tasks and various set of procedures that is called as reduce the complexity through several stages of verification software system engineering (SwSE).This SwSE can be and validation. specifically applied in the development of large complex Software System Engineering Requirement Design Planning Managing Verification, Validation, Analysis Testing Fig .1. Phases in Software System engineering activities to determine that they are following the technical Software system Engineering manages the technical function and managerial plans, specifications, standards, and of the system products which produces the documents for procedures. V&V. evaluate the interim and final product of reference. Evaluation criteria, a series of steps or an iterative software engineering. process using genetic algorithms can give this documentation reference. The user satisfaction must meet out through the system engineers. The success of software development process and To achieve a successful process, planning is necessary. the system life cycles undergoes much revaluation process to Planning tells us the goals in a project the objectives, redefine the functional requirements. strategies, polices, plans, and procedure. It tells us in advance what, how, when and who will do the process. To plan a 2.1 Requirement Analysis software engineering project we need SWSE management The first step in any software development activity is to activities that lead in selecting a course of action from determine and document the system-level requirements in alternative possibilities and defining a program for completing either a system requirements specification (SRS) or a software those actions. requirements specification or both. Software requirements The collection of management activities that used to ensure include capabilities that a user needs to solve a problem or that the project goes according to the plan is known as process achieve an objective as well as capabilities that a system or control. The performance and results against plans, notes component needs to satisfy a contract, standard, or other deviations measured using process control. It takes corrective formally imposed document. Software requirements analysis actions to ensure conformance between plans and actual begins after system engineering has defined the acquirer and results. Process control gives us a feedback to the system for user system requirements. Its functions include identification how well the project is going. In system, engineering V&V is of all – or as many as possible – software system a continuous process of-monitoring system engineering, requirements, and its conclusion marks the established SwSE, software engineering, and project management requirements baseline, sometimes called the allocated baseline [3]. Requirement Analysis Functional Requirement Non-Functional Analysis Requirement Analysis User Interface Performance Transaction Performance External Interface Auditing Design Constraints Quality Attributes Authentication Fig.2. Software Requirement Analysis We can categorize software requirements as shown in Fig.2.Functional requirements specify functions that a Authentication www.ijert.org 2
  • 3. International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 1 Issue 5, July - 2012 system or system component must be capable of o Identification performing. o Reaction Non-Functional requirements, which include the o Behavior Performance requirements, specify performance Transaction based performance characteristics that a system or system component must possess such as speed, accuracy, and frequency. External o Identification interface requirements specify hardware, software, or database elements with which a system or component o Reaction must interface, or set forth constraints on formats, o Behavior timing, or other factors caused by such an interface. Design constraints affect or constrain the design of a Auditing software system or software system component, for o Functions example, language requirements, physical hardware requirements, software development standards, and o Limitations software quality assurance standards. Quality attributes specify the degree to which software possesses attributes Authentication that affect quality, such as correctness, reliability, o Members maintainability, and portability. o Managers o Administrators. 3. FUNCTIONAL REQUIREMENTS In software system engineering, a functional requirement defines a function of a software system or its component. A function is described as a set of inputs, the behavior, and outputs. Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describing all the cases where the system 3.1 Model system for functional uses the functional requirements are captured in use cases. Functional requirements are supported by non- Requirements: functional requirements, which impose constraints on The representation for the requirement starts from the the design or implementation, such as performance world view to the design view. This may be a top down requirements, security, or reliability. Acceptable systems or bottom up approach. A system should be modeled, must satisfy all the mandatory requirements. [12] which has an element and also plays a vital role in the development process [9] [10]. Functional requirements are based on the following four classical members have been depicted in Fig .3 as, Now the modeled developed is top down approach, so it starts form Defining the processes Represent the behavior of the processes User Interface assumptions on which the behavior is based. Explicitly define the exogenous end Functional endogenous input to the model. Requirements Represent all the links. Auditing Authentication In constructing a model, the restraining factors such as assumptions, simplifications, limitations and constraints must be considered. Representing the requirements in World view (WV) as, WV D1 , D2 , D3 ..., Dn Fig.3. Classification of Functional Requirements. Di D1 , D2 , D3 ..., Dn Di are the Set of domains either systems / subsystems. Representing the requirement as Domain view (DV), DV E1 , E2 , E3 ,...Em Retrieving input from the user www.ijert.org 3
  • 4. International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 1 Issue 5, July - 2012 Ej E1 , E2 , E3 ,..., Em engineering plays in complex projects. An Heuristic approach which will optimize the Ej are the set of elements which satisfies the objective or complex problems through various techniques. the goal of accomplished tasks. These techniques and methods leads to feasible Representing the Elemental view (EV) as, solution through LPPs. There are various methods through which optimal solution can be obtained. EV C1 , C2 , C3 ,...Ck Like, Least cost method, North west corner rule, Ck C1 , C2 , C3 ,..., Ck Traveling sales person problem[19]. Ck are the set of technical components that achieves the necessary function of an element [3]. These assumptions shown in Fig.4, of world, domain, elementary and components of the can be evaluated via a genetic algorithmic approach. World View( Requirement analysis) Domain View 1( Functional) Domain View 2(Non- Functional) Elementary View 1(Retreiving Elementary View2 Transaction Elementary View 3 Auditing Input from the user) Performance Operations research, briefly, is concerned with the optimization of a process under multiple Detailed view1 Detailed view2 Detailed view3 … constraints. This paper takes into consideration the Identification Reaction Behavior optimization technique – assignment problem, which helps to have minimal time period and can achieve an approximate solution which is responsible for preparing a decision making system. Fig. 4. A Model Representation - Functional requirements. This decision can be applied to complex programs. It is taken into consideration that constraints at 4. EVALUATION OF REQUIREMENTS various levels. THROUGH AN LPP The Assignment Problem The simple assignment problem which helps to 4.1 Operation Research In System optimize and reduce the cost of the product. On the Engineering basis of the output, the product will be identified to be an optimized. This will help the software Operations research supports systems organization to identify the minimum cost of the engineering. The tools of operations research are product and cost taken to complete the process. used in systems analysis, decision making, and trade studies. Highlights the role systems www.ijert.org 4
  • 5. International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 1 Issue 5, July - 2012 An assignment problem is a special type of row, and is the assignment that minimizes risk of linear programming problem where the objective is the requirement analysis. to minimize the cost or time of completing a number of jobs by a number of persons [20]. A typical assignment problem, presented in the classic manner, is shown in Fig. 12. Here there are five customers to be assigned to five requirements. The numbers in the matrix indicate the cost of doing each requirement analysis with each module. project with costs of M are disallowed Figure 7. Solution to the requirement optimization assignments. The problem is to find the minimum Problem time to matching the requirements to products. so, in searching a large state-space, multi-modal state-space, or n-dimensional surface, a genetic algorithm may offer significant benefits over more typical search of Optimization Techniques. (linear programming, heuristic, depth-first, breath-first, and praxis.) 5. CONCLUSION Figure.5. Matrix model of the requirements. Software System Engineering performs a variety of functions at various stages in the product The network model is in Fig. 6. It is very similar to development life cycle. Software Requirement the transportation model except the external flows Analysis is a phase in which reevaluation has to be are all +1 or -1. The only relevant parameter for started. Requirements are classified into functional the assignment model is arc cost (not shown in the and non-functional requirements relevant to the figure for clarity) ; all other parameters should be product or process developed. The functional set to default values. The assignment network also requirements categorized as, user interface, has the bipartite structure. transaction performance, auditing and authentication were done in accordance with their functions. The basic representation which is relevant to software system engineering such as world, domain, elementary and component view were discussed. The views noted have been approached from top - down. This paper focuses on using the LPP to have an iterative process of identifying and refining the requirements by a method of reevaluation. A series of repeated steps using the tool will help us to elicit all the requirements to develop the design phase successfully. 6. REFERENCES [1] A.Terry Bahill, Clark Biggs, “ The Systems Engineering started in the middle process: a consensus of system Engineers and project Mangers, 2001, John Wiley & sons, Inc.syst Eng:156 – 157. Figure 6. Network model of the requirements. [2] Eushiuan Tran , “ Requirements & Specification” The solution to the assignment problem as shown in Fig. 7 has a total flow of 1 in every column and [3] Quantifying Software Reliability Readiness Astana, A.; Olivieri, J. ; Alcatel - Lucent, Westford, MA, USA www.ijert.org 5
  • 6. International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 1 Issue 5, July - 2012 [4] Software Engineering a Practioner’s Approach, sixth Edition, Roger S.Pressman. [5] Software Engineering Theory and Practice, Fourth Edition, Shari Lawerence Fleeger, Joanne M. Atlee. [6] A. J. Chipperfield and P. J. Fleming, the MATLAB Genetic Algorithm Toolbox. [7] Richard H.Thayer, “Software System Engineering: A Tutorial”IEEE 2002, pp 68-73. [8] Eric C.Honour, “ Understanding the Value of System Engineering” [9] “Introduction to Systems Engineering” [10] Linda Westfall, “Software Requirements Engineering: What, Why, Who, When, and How”, 2005-2006. [11] Dr.Judith Dahmann, “Importance of systems engineering in Early Acquisition”. [12] www.ofnisystems.com/Validation/Functional_Req uirements.htm [13] Terry Bahill, “The Eight System Engineering Documents”, 2001-2009. [14] A.Terry Bahill, Frank F. Dean, “What is system engineering? A consensus of senior system Engineers”, Jan 15, 2009. [15] Dr. Laurie Williams, “ A (Partial) Introduction to Software Engineering Practices and Methods”, NCSU CSC326 Course Pack, 2008-2009 (Fifth) Editions. [16] Prof. Dr. Oscar Nierstrasz, Dr. St´ephane DucasseMichele Lanza, “Recovering the Evolution of Object Oriented SoftwareSystems Using a Flexible Query Engine”, June 2001. [17] Ruth Malan and Dana Bredemeyer “Functional Requirements and Use Cases”. [18] http://media.wiley.com/product_data/excerpt/96/ 07695119/0769511996.pdf. [19] http://businessmanagementcourses.org/Lesson19 AssignmentProblem.pdf [20] Operations Research: An Introduction (7th Edition) Hamdy A. Taha [21] Quantifying Software Reliability Readiness Asthana, A.; Olivieri, J.; Alcatel-Lucent, Westford, MA, USA www.ijert.org 6