The Experts below are selected from a list of 231 Experts worldwide ranked by ideXlab platform

Dharmender Singh Kushwaha - One of the best experts on this subject based on the ideXlab platform.

  • Natural language based component extraction from requirement Engineering Document and its complexity analysis
    ACM SIGSOFT Software Engineering Notes, 2011
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    Requirement Engineering Document (IEEE-830: 1998) plays a very significant role in software development. The size and complexity of software systems are continuously increasing. As scale changes to more complex and larger systems, new problems occur that did not exist in smaller systems This leads to redefining priorities of the activities that go into developing software. As systems ges complex, it becomes evident that the goals of the entire system can't be easily comprehended. Hence the need of more rigorous requirement analysis arises. The requirement analyst has to identify the requirements by using various methods like interviews, brainstorming, FAST (facilitated application specification techniques), quality function deployment, use-case etc. To overcome these issues, this paper proposes object based semi-automated system that categorize the requirements and further identifies the component based on requirement Engineering Document in a component library and further analyses the complexity of components and its usage.

  • A metric suite for early estimation of software testing effort using requirement Engineering Document and its validation
    2011 2nd International Conference on Computer and Communication Technology, ICCCT-2011, 2011
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    Software testing is one of the most important and critical activity of software development life cycle which ensures software quality and directly influences the development cost and success of the software. This paper empirically proposes a test metric for the estimation of the software testing effort using IEEE-Software Requirement Specification (SRS) Document in order to avoid budget overshoot, schedule escalation etc., at very early stage of software development. Further the effort required to develop or test the software will also depend on the complexity of the proposed software. Therefore the proposed test metric computes the requirement based complexity for yet to be developed software on the basis of SRS Document. Later the proposed measure is also compared with other proposals for test effort estimation like code based, cognitive value based and use case based measures. The result obtained validates that the proposed test metric is a comprehensive one and compares well with various other prominent measures. The computation of proposed test effort estimation involves least overhead as compared to others.

  • complexity measure based on requirement Engineering Document and its validation
    International Conference on Computer and Communication Technology, 2010
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    The various complexity measure established so far are based on code and cognitive value of the software. It is established that a high quality SRS is pre requisite for high quality software, hence this work attempts to empirically demonstrate that the complexity of the code to be produced can be determined based on IEEE software requirement specification Document (IEEE 830–1993). Considering the shortcoming of code based approaches, the proposed approach is able to compute the complexity of yet to be coded software immediately after freezing the requirement in SDLC (Software Development Life Cycle) process. Results obtained show that the complexity values are comparable with other established measures and hence the complexity of the software to be produced could be computed from SRS Documents. Its validity is established by evaluating proposed measure against Weyuker properties.

  • Early estimation of software complexity using requirement Engineering Document
    ACM SIGSOFT Software Engineering Notes, 2010
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    There has been a continuous effort to estimate software complexity but very little established methods exist that can estimate the complexity of the software before it is written. Since a high quality Software Requirement Specification (SRS) is a pre requisite for high quality software, this work attempts to empirically demonstrate that the complexity of the code can be determined based on its IEEE software requirement specification Document (IEEE 830-1998). Existing complexity measures established are based on the code and the cognitive metrics value of the software. This may require recodingleading to loss of time and cost. Considering the shortcoming of code-based approaches, our proposed approach is able to compute the complexity of yet-to-be-written software immediately after freezing the requirement in the Software development Lifecycle (SDLC) process. The proposedcomplexity measure compares well with established complexity measures like Halstead, Mc Cabe, KLCID, CFS and CICM. Results obtained show that the complexity values are comparable with other established measures. The robustness of our complexity measure is established by evaluating our measure against Weyuker properties.

  • A Complexity measure based on Requirement Engineering Document
    arXiv: Software Engineering, 2010
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    Research shows, that the major issue in development of quality software is precise estimation. Further this estimation depends upon the degree of intricacy inherent in the software i.e. complexity. This paper attempts to empirically demonstrate the proposed complexity which is based on IEEE Requirement Engineering Document. It is said that a high quality SRS is pre requisite for high quality software. Requirement Engineering Document (SRS) is a specification for a particular software product, program or set of program that performs some certain functions for a specific environment. The various complexity measure given so far are based on Code and Cognitive metrics value of software, which are code based. So these metrics provide no leverage to the developer of the code. Considering the shortcoming of code based approaches, the proposed approach identifies complexity of software immediately after freezing the requirement in SDLC process. The proposed complexity measure compares well with established complexity measures. Finally the trend can be validated with the result of proposed measure. Ultimately, Requirement based complexity measure can be used to understand the complexity of proposed software much before the actual implementation of design thus saving on cost and manpower wastage.

Reijo Sulonen - One of the best experts on this subject based on the ideXlab platform.

  • an Engineering Document management system1
    2007
    Co-Authors: Hannu Peltonen, Kari Alho, Tomi Männistö, Reijo Sulonen
    Abstract:

    Hannu Peltonen, Tomi Mannisto, Kari Alho, Reijo SulonenHelsinki University of TechnologyLaboratory of Information Processing ScienceOtakaari 1, 02150 Espoo, FinlandE-mail: hpe@cs.hut.fiAbstractThe implementation of an Engineering data management system(EDMS) is described. The system models CAD drawings and otherEngineering Documents as objects, which can be composed of subdocu-ments and have multiple versions and representations.Documents contain user-defined attributes and the actual data forseparate CAD tools. The Documents are accessed with a server pro-gram, which stores Document contents and attributes in a repositorybuilt on top of a relational database. The server accepts service requestsfrom various client programs, including a graphical user interface.Document approval and release procedures can be described bymeans of user-defined state graphs. Access rights are controlled in aflexible manner with an authorization program. Attributes can betreated as active data by means of procedures which enforce dependen-cies between attribute values.

  • process based view of product data management
    Computers in Industry, 1996
    Co-Authors: Hannu Peltonen, Olli Pitkänen, Reijo Sulonen
    Abstract:

    Copyright (c) 1997 Elsevier Science B.V. All rights reserved. Many companies consider acquiring a product data management system (PDMS) to reduce the delays and costs caused by inefficient product data management. There are, however, considerable differences between the various commercially available PDMSs, starting from the different meanings of basic concepts, such as Document or Document version. Before evaluating various PDMSs and their features, a company should analyze the processes in which the PDMS is going to be used. This paper describes two common processes: the development and delivery processes of configurable products. To a large extent product data is expressed as Documents, and consequently Engineering Document management is one of the main functions of a PDMS. The rest of the paper discusses general requirements for Document management within a PDMS and the particular requirements implied by the two process types.

  • Process-based view of product data management
    Computers in Industry, 1996
    Co-Authors: Hannu Peltonen, Olli Pitkänen, Reijo Sulonen
    Abstract:

    Abstract Many companies consider acquiring a product data management system (PDMS) to reduce the delays and costs caused by inefficient product data management. There are, however, considerable differences between the various commercially available PDMSs, starting from the different meanings of basic concepts, such as Document or Document version. Before evaluating various PDMSs and their features, a company should analyze the processes in which the PDMS is going to be used. This paper describes two common processes: the development and delivery processes of configurable products. To a large extent product data is expressed as Documents, and consequently Engineering Document management is one of the main functions of a PDMS. The rest of the paper discusses general requirements for Document management within a PDMS and the particular requirements implied by the two process types.

  • An Authorization Mechanism for a Document Database
    ASME 1994 8th Annual Database Symposium, 1994
    Co-Authors: Kari Alho, Hannu Peltonen, Tomi Männistö, Reijo Sulonen
    Abstract:

    Abstract A programmable authorization mechanism for an Engineering Document database is described. The database stores Documents and their versions in a commercial relational database. Documents and other objects contain user-defined attributes. Release and approval procedures of the Documents are described by means of state graphs that specify the possible states of a Document and the transitions between them. The system consists of centralized server and client programs, which communicate with the server using a specific protocol. The database administrator must be able to formulate rules that tell who is allowed to do particular database operations; rules that tell which operations are allowed in particular Document states; and rules that describe consistency invariants between attributes. These rules are expressed by means of authorization procedures written in a special language. Whenever the server receives an operation request, it executes the corresponding authorization procedure. The system can thus be easily adapted to an organization without actually modifying the client or server programs.

Ajit Sharma - One of the best experts on this subject based on the ideXlab platform.

  • Natural language based component extraction from requirement Engineering Document and its complexity analysis
    ACM SIGSOFT Software Engineering Notes, 2011
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    Requirement Engineering Document (IEEE-830: 1998) plays a very significant role in software development. The size and complexity of software systems are continuously increasing. As scale changes to more complex and larger systems, new problems occur that did not exist in smaller systems This leads to redefining priorities of the activities that go into developing software. As systems ges complex, it becomes evident that the goals of the entire system can't be easily comprehended. Hence the need of more rigorous requirement analysis arises. The requirement analyst has to identify the requirements by using various methods like interviews, brainstorming, FAST (facilitated application specification techniques), quality function deployment, use-case etc. To overcome these issues, this paper proposes object based semi-automated system that categorize the requirements and further identifies the component based on requirement Engineering Document in a component library and further analyses the complexity of components and its usage.

  • A metric suite for early estimation of software testing effort using requirement Engineering Document and its validation
    2011 2nd International Conference on Computer and Communication Technology, ICCCT-2011, 2011
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    Software testing is one of the most important and critical activity of software development life cycle which ensures software quality and directly influences the development cost and success of the software. This paper empirically proposes a test metric for the estimation of the software testing effort using IEEE-Software Requirement Specification (SRS) Document in order to avoid budget overshoot, schedule escalation etc., at very early stage of software development. Further the effort required to develop or test the software will also depend on the complexity of the proposed software. Therefore the proposed test metric computes the requirement based complexity for yet to be developed software on the basis of SRS Document. Later the proposed measure is also compared with other proposals for test effort estimation like code based, cognitive value based and use case based measures. The result obtained validates that the proposed test metric is a comprehensive one and compares well with various other prominent measures. The computation of proposed test effort estimation involves least overhead as compared to others.

  • complexity measure based on requirement Engineering Document and its validation
    International Conference on Computer and Communication Technology, 2010
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    The various complexity measure established so far are based on code and cognitive value of the software. It is established that a high quality SRS is pre requisite for high quality software, hence this work attempts to empirically demonstrate that the complexity of the code to be produced can be determined based on IEEE software requirement specification Document (IEEE 830–1993). Considering the shortcoming of code based approaches, the proposed approach is able to compute the complexity of yet to be coded software immediately after freezing the requirement in SDLC (Software Development Life Cycle) process. Results obtained show that the complexity values are comparable with other established measures and hence the complexity of the software to be produced could be computed from SRS Documents. Its validity is established by evaluating proposed measure against Weyuker properties.

  • Early estimation of software complexity using requirement Engineering Document
    ACM SIGSOFT Software Engineering Notes, 2010
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    There has been a continuous effort to estimate software complexity but very little established methods exist that can estimate the complexity of the software before it is written. Since a high quality Software Requirement Specification (SRS) is a pre requisite for high quality software, this work attempts to empirically demonstrate that the complexity of the code can be determined based on its IEEE software requirement specification Document (IEEE 830-1998). Existing complexity measures established are based on the code and the cognitive metrics value of the software. This may require recodingleading to loss of time and cost. Considering the shortcoming of code-based approaches, our proposed approach is able to compute the complexity of yet-to-be-written software immediately after freezing the requirement in the Software development Lifecycle (SDLC) process. The proposedcomplexity measure compares well with established complexity measures like Halstead, Mc Cabe, KLCID, CFS and CICM. Results obtained show that the complexity values are comparable with other established measures. The robustness of our complexity measure is established by evaluating our measure against Weyuker properties.

  • A Complexity measure based on Requirement Engineering Document
    arXiv: Software Engineering, 2010
    Co-Authors: Ajit Sharma, Dharmender Singh Kushwaha
    Abstract:

    Research shows, that the major issue in development of quality software is precise estimation. Further this estimation depends upon the degree of intricacy inherent in the software i.e. complexity. This paper attempts to empirically demonstrate the proposed complexity which is based on IEEE Requirement Engineering Document. It is said that a high quality SRS is pre requisite for high quality software. Requirement Engineering Document (SRS) is a specification for a particular software product, program or set of program that performs some certain functions for a specific environment. The various complexity measure given so far are based on Code and Cognitive metrics value of software, which are code based. So these metrics provide no leverage to the developer of the code. Considering the shortcoming of code based approaches, the proposed approach identifies complexity of software immediately after freezing the requirement in SDLC process. The proposed complexity measure compares well with established complexity measures. Finally the trend can be validated with the result of proposed measure. Ultimately, Requirement based complexity measure can be used to understand the complexity of proposed software much before the actual implementation of design thus saving on cost and manpower wastage.

Hannu Peltonen - One of the best experts on this subject based on the ideXlab platform.

  • an Engineering Document management system1
    2007
    Co-Authors: Hannu Peltonen, Kari Alho, Tomi Männistö, Reijo Sulonen
    Abstract:

    Hannu Peltonen, Tomi Mannisto, Kari Alho, Reijo SulonenHelsinki University of TechnologyLaboratory of Information Processing ScienceOtakaari 1, 02150 Espoo, FinlandE-mail: hpe@cs.hut.fiAbstractThe implementation of an Engineering data management system(EDMS) is described. The system models CAD drawings and otherEngineering Documents as objects, which can be composed of subdocu-ments and have multiple versions and representations.Documents contain user-defined attributes and the actual data forseparate CAD tools. The Documents are accessed with a server pro-gram, which stores Document contents and attributes in a repositorybuilt on top of a relational database. The server accepts service requestsfrom various client programs, including a graphical user interface.Document approval and release procedures can be described bymeans of user-defined state graphs. Access rights are controlled in aflexible manner with an authorization program. Attributes can betreated as active data by means of procedures which enforce dependen-cies between attribute values.

  • process based view of product data management
    Computers in Industry, 1996
    Co-Authors: Hannu Peltonen, Olli Pitkänen, Reijo Sulonen
    Abstract:

    Copyright (c) 1997 Elsevier Science B.V. All rights reserved. Many companies consider acquiring a product data management system (PDMS) to reduce the delays and costs caused by inefficient product data management. There are, however, considerable differences between the various commercially available PDMSs, starting from the different meanings of basic concepts, such as Document or Document version. Before evaluating various PDMSs and their features, a company should analyze the processes in which the PDMS is going to be used. This paper describes two common processes: the development and delivery processes of configurable products. To a large extent product data is expressed as Documents, and consequently Engineering Document management is one of the main functions of a PDMS. The rest of the paper discusses general requirements for Document management within a PDMS and the particular requirements implied by the two process types.

  • Process-based view of product data management
    Computers in Industry, 1996
    Co-Authors: Hannu Peltonen, Olli Pitkänen, Reijo Sulonen
    Abstract:

    Abstract Many companies consider acquiring a product data management system (PDMS) to reduce the delays and costs caused by inefficient product data management. There are, however, considerable differences between the various commercially available PDMSs, starting from the different meanings of basic concepts, such as Document or Document version. Before evaluating various PDMSs and their features, a company should analyze the processes in which the PDMS is going to be used. This paper describes two common processes: the development and delivery processes of configurable products. To a large extent product data is expressed as Documents, and consequently Engineering Document management is one of the main functions of a PDMS. The rest of the paper discusses general requirements for Document management within a PDMS and the particular requirements implied by the two process types.

  • An Authorization Mechanism for a Document Database
    ASME 1994 8th Annual Database Symposium, 1994
    Co-Authors: Kari Alho, Hannu Peltonen, Tomi Männistö, Reijo Sulonen
    Abstract:

    Abstract A programmable authorization mechanism for an Engineering Document database is described. The database stores Documents and their versions in a commercial relational database. Documents and other objects contain user-defined attributes. Release and approval procedures of the Documents are described by means of state graphs that specify the possible states of a Document and the transitions between them. The system consists of centralized server and client programs, which communicate with the server using a specific protocol. The database administrator must be able to formulate rules that tell who is allowed to do particular database operations; rules that tell which operations are allowed in particular Document states; and rules that describe consistency invariants between attributes. These rules are expressed by means of authorization procedures written in a special language. Whenever the server receives an operation request, it executes the corresponding authorization procedure. The system can thus be easily adapted to an organization without actually modifying the client or server programs.

N H Dehkordi - One of the best experts on this subject based on the ideXlab platform.

  • plutonium finishing plant pfp standby power system commercial grade item cgi critical characteristics
    Other Information: PBD: 12 Apr 2000, 2000
    Co-Authors: N H Dehkordi
    Abstract:

    PFP's Standby Power System consists of the diesel generators, the generator control system, Rm 308 UPS, switchgear batteries, and the electrical equipment used to distribute this power. Due to the nature of the equipment and its use throughout general industry, the majority of the system falls within the CGI definition HNF-PRO-268, ''Control of Purchased Items and Services'' and HNF-PRO-1819, ''PHMC Engineering Requirements'' require that the critical characteristics of CGI-procured equipment be established in an Engineering Document prior to placing the order. HNF-5043 established these critical characteristics for the Standby Power System. This modification adds several items to the Document.