General Discussion about SIT,GUA,Smart ETL tools and SMS blocker
Scope of Project:
<Write here in detail about the scope of your project>
Functional and non Functional Requirements:
<Write here in detail about the functional and non-functional requirements of your system in separate headings>
Use Case Diagram(s):
<Provide here the use case diagram of your system>
<Provide here the usage scenarios of all use cases in table format explaining Use Case title, Use Case Id, Actions, Description, Alternative Paths, Pre and Post Conditions, Author, Exceptions. You are supposed to provide a usage scenario for each of use case shown in use case diagram>
<Write here detail about the adopted methodology for your project. You must choose VU Process Model which is a combination of waterfall and spiral models. More or combining two or more methodologies is explained in SE2 (CS605) handouts. >
Work Plan (Use MS Project to create Schedule/Work Plan)
<Provide Gantt chart of your final project>
mera srs ka submit ka buton nai show ho raha . ku?
Apny project supervisor ko mail kar do.....
plzzzzz discuss Functional and non Functional Requirements:
A functional requirement describes what a software system should do, while non-functional requirements place constraints on how the system will do so.The functional requirement is describing the behavior of the system as it relates to the system's functionality. The non-functional requirement elaborates a performance characteristic of the system.
There are total 5 topics in SRS.. i'm going to discuss all 5 one by one.
Yes , but Inam bro scope hum discuss kr chuky hein Functional , Non Functional requirements discuss kry gy ,
The next level of detail comes in the form of what is called functional requirements. They bring-in the system’s view and define from the system’s perspective the software functionality the developers must build into the product to enable users to accomplish their tasks stated in the user requirements - thereby satisfying the business requirements.
Functional requirements define the internal workings of the software: that is, the calculations, technical details, data manipulation and processing and other specific functionality. They are supported by non-functional requirements, which impose constraints on the design or implementation (such as performance requirements, security, quality standards, or design constraints). Functional requirements capture the intended behavior of the system. This behavior may be expressed as services, tasks or functions the system is required to perform.
Typically, a requirements analyst generates functional requirements after building use cases. However this may have exceptions since software development is an iterative process and sometimes certain requirements are conceived prior to the definition of the use cases. Both artifacts (use cases documents and requirements documents) complement each other in a bidirectional process.
A typical functional requirement will contain a unique name and number, a brief summary. This information is used to help the reader understand why the requirement is needed, and to track the requirement through the development of the system.
The core of the requirement is the description of the required behavior, which must be a clear and readable description of the required behavior. This behavior may come from organizational or business rules, or it may be discovered through elicitation sessions with users, stakeholders, and other experts within the organization. Many requirements will be uncovered during the use case development. When this happens, the requirements analyst should create a placeholder requirement with a name and summary, and research the details later, to be filled in when they are better known.
Software requirements must be clear, correct, unambiguous, specific, and verifiable.
Functional requirements are typically phrased with subject/predicate constructions, or noun/verb. "The system prints invoices."
Non-functional requirements may be found in adverbs or modifying clauses, such as
"The system prints invoices *quickly*"
"The system prints invoices *with confidentiality*".
From a mathematical point of view, a "function" takes an input(s) and yields an output(s). "Functional" refers to the set of functions the system it to offer, while "non-functional" refers to the manner in which such functions are performed.
Following are IEEE definitions:
Functional requirement: A system/software requirement that specifies a function that a system/ software system or system/software component must be capable of performing.
These are software requirements that define behavior of the system, that is, the fundamental process or transformation that software and hardware components of the system perform on inputs to produce outputs.
Functional Requirements are a key area of project management and they are very important system requirements in the system design process. These requirements are the technical specifications, system design parameters and guidelines, data manipulation, data processing, and calculation modules etc, of the proposed system.
Functional Requirements are in contrast to Non-Functional Requirements which are descriptive of the parameters of system performance, quality attributes, reliability and security, cost, constraints in design/implementation, etc. The key goal of determining “functional requirements” is to capture the required behavior of a system in terms of functionality.
Listed below are a total of fifty examples of functional requirements. These examples are from five basic systems:
The Functional Requirements Are Given In The Project File.
For Example For GUA Students some Functional Requirements Are
On the basis of functional requirement we can make use case diagram. First check that how many user are in project. then check that task they will perform.
Good work Inam bhai . keep it up
USE CASE Diagram
use case is the simply how the systems is going to be used .