Patents
Literature
Patsnap Copilot is an intelligent assistant for R&D personnel, combined with Patent DNA, to facilitate innovative research.
Patsnap Copilot

57 results about "Non-functional requirement" patented technology

In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. They are contrasted with functional requirements that define specific behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture, because they are usually architecturally significant requirements.

Method for improving execution efficiency of a software package customization

A method for improving execution efficiency of a software package customization is disclosed. The method includes identifying one or more components from a configuration table to implement at least one of a use case flow or a non functional requirement (NFR) or an interface document or combinations thereof derived using an use case of the software project, sequencing the identified one or more components to prioritize execution of the use case of the software project and attributing complexity of the identified one or more components to determine the effort estimation for execution of the use case, wherein the attributing complexity includes using an unit effort table for determining the effort estimation requirement for execution of each component of the use case. The method further includes identifying a usage type, attributing the reuse level and resolving the dependencies among the identified components. The usage type of the identified component is selected from the group consists of build afresh, customization, an out of box (OOB) or duplicate. The effort estimation required for customization or OOB of the identified components is percentage indicative of the effort estimation required for build a fresh type. The reuse level of the identified component is determined based on the availability the components in past use cases. The method also includes identifying the additional activities required for developing the identified components or the use case or the software project. In another embodiment of the present invention, a method to perform the gap analysis post requirements gathering of a software project to act as a precursor for a detailed design of the software project is disclosed. In yet another embodiment of the present invention, the method of enhancing the efficiency of a project planning of a software project is also disclosed.
Owner:INFOSYS LTD
Who we serve
  • R&D Engineer
  • R&D Manager
  • IP Professional
Why Eureka
  • Industry Leading Data Capabilities
  • Powerful AI technology
  • Patent DNA Extraction
Social media
Try Eureka
PatSnap group products