SlideShare una empresa de Scribd logo
1 de 2
Descargar para leer sin conexión
Functional specification:

        A functional specification (or sometimes functional specifications) is a formal document 
used to describe in detail for software developers a product's intended capabilities, appearance, and 
interactions with users. The functional specification is a kind of guideline and continuing reference 
point as the developers write the programming code. (At least one major product development group 
used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for 
a word processing system, then declared that the user's guide was the functional specification. The 
developers were challenged to create a product that matched what the user's guide described.) 
Typically, the functional specification for an application program with a series of interactive 
windows and dialogs with a user would show the visual appearance of the user interface and 
describe each of the possible user input actions and the program response actions. A functional 
specification may also contain formal descriptions of user tasks, dependencies on other products, 
and usability criteria. Many companies have a guide for developers that describes what topics any 
product's functional specification should contain. 

        For a sense of where the functional specification fits into the development process, here are a 
typical series of steps in developing a software product: 

    • Requirements. This is a formal statement of what the product planners informed by their 
      knowledge of the marketplace and specific input from existing or potential customers believe 
      is needed for a new product or a new version of an existing product. Requirements are 
      usually expressed in terms of narrative statements and in a relatively general way. 
    • Objectives. Objectives are written by product designers in response to the Requirements. 
      They describe in a more specific way what the product will look like. Objectives may 
      describe architectures, protocols, and standards to which the product will conform. 
      Measurable objectives are those that set some criteria by which the end product can be 
      judged. Measurability can be in terms of some index of customer satisfaction or in terms of 
      capabilities and task times. Objectives must recognize time and resource constraints. The 
      development schedule is often part or a corollary of the Objectives. 
    • Functional specification. The functional specification (usually functional spec or just spec 
      for short) is the formal response to the objectives. It describes all external user and 
      programming interfaces that the product must support. 
    • Design change requests. Throughout the development process, as the need for change to the 
      functional specification is recognized, a formal change is described in a design change 
      request. 
    • Logic specification. The structure of the programming (for example, major groups of code 
      modules that support a similar function), individual code modules and their relationships, 
      and the data parameters that they pass to each other may be described in a formal document 
      called a logic specification. The logic specification describes internal interfaces and is for 
      use only by the developers, testers, and, later, to some extent, the programmers that service 
      the product and provide code fixes to the field. 
    • User documentation. In general, all of the preceding documents (except the logic 
      specification) are used as source material for the technical manuals and online information 
      (such as help pages) that are prepared for the product's users. 
• Test plan. Most development groups have a formal test plan that describes test cases that 
      will exercise the programming that is written. Testing is done at the module (or unit) level, at 
      the component level, and at the system level in context with other products. This can be 
      thought of as alpha testing. The plan may also allow for beta test. Some companies provide 
      an early version of the product to a selected group of customers for testing in a "real world" 
      situation. 
    • The final product. Ideally, the final product is a complete implementation of the functional 
      specification and design change requests, some of which may result from formal testing and 
      beta testing. 
       The cycle is then repeated for the next version of the product, beginning with a new 
Requirements statement, which ideally uses feedback from customers about the current product to 
determine what customers need or want next. 
        Most software makers adhere to a formal development process similar to the one described 
above. The hardware development process is similar but includes some additional considerations for 
the outsourcing of parts and verification of the manufacturing process itself. 

Más contenido relacionado

Destacado

Word processing software
Word processing softwareWord processing software
Word processing softwareGARY MOHAN
 
Word processing
Word processing Word processing
Word processing Johan Koren
 
Word processing software
Word processing software Word processing software
Word processing software itsrahul07
 
TID Chapter 4 Introduction To Spreadsheet(Excel)
TID Chapter 4 Introduction To Spreadsheet(Excel)TID Chapter 4 Introduction To Spreadsheet(Excel)
TID Chapter 4 Introduction To Spreadsheet(Excel)WanBK Leo
 
Computer hardware component Created by king parmeshwar pawar
Computer hardware component Created by king parmeshwar pawarComputer hardware component Created by king parmeshwar pawar
Computer hardware component Created by king parmeshwar pawarKing Parmeshwar Pawar :) Edu.Li
 
Word Processing Powerpoint
Word Processing PowerpointWord Processing Powerpoint
Word Processing Powerpointthomsonc4000
 
Word Processing Presentation
Word Processing PresentationWord Processing Presentation
Word Processing Presentationthomasl2000
 
Introduction to word processing
Introduction to word processingIntroduction to word processing
Introduction to word processingNerissa Tan
 

Destacado (9)

Word processing software
Word processing softwareWord processing software
Word processing software
 
Word processing
Word processing Word processing
Word processing
 
Word processing software
Word processing software Word processing software
Word processing software
 
TID Chapter 4 Introduction To Spreadsheet(Excel)
TID Chapter 4 Introduction To Spreadsheet(Excel)TID Chapter 4 Introduction To Spreadsheet(Excel)
TID Chapter 4 Introduction To Spreadsheet(Excel)
 
Computer hardware component Created by king parmeshwar pawar
Computer hardware component Created by king parmeshwar pawarComputer hardware component Created by king parmeshwar pawar
Computer hardware component Created by king parmeshwar pawar
 
Word Processing Powerpoint
Word Processing PowerpointWord Processing Powerpoint
Word Processing Powerpoint
 
Word Processing Presentation
Word Processing PresentationWord Processing Presentation
Word Processing Presentation
 
Word Processing Ppt
Word Processing PptWord Processing Ppt
Word Processing Ppt
 
Introduction to word processing
Introduction to word processingIntroduction to word processing
Introduction to word processing
 

Similar a Fs

Design submission template
Design submission templateDesign submission template
Design submission templatekrudee
 
400-600 wordsAPA format with referencesOne of the first ta.docx
400-600 wordsAPA format with referencesOne of the first ta.docx400-600 wordsAPA format with referencesOne of the first ta.docx
400-600 wordsAPA format with referencesOne of the first ta.docxBHANU281672
 
Software Requirements SpecificationforProjectVersion.docx
Software Requirements SpecificationforProjectVersion.docxSoftware Requirements SpecificationforProjectVersion.docx
Software Requirements SpecificationforProjectVersion.docxrosemariebrayshaw
 
Lecture 5 defining the system
Lecture 5 defining the systemLecture 5 defining the system
Lecture 5 defining the systemShahid Riaz
 
Notes on software engineering
Notes on software engineeringNotes on software engineering
Notes on software engineeringErtan Deniz
 
Requirement Engineering Processes & Eliciting Requirement
Requirement Engineering Processes & Eliciting Requirement Requirement Engineering Processes & Eliciting Requirement
Requirement Engineering Processes & Eliciting Requirement AqsaHayat3
 
Software Requirements SpecificationforProjectVersion 1.0 a.docx
Software Requirements SpecificationforProjectVersion 1.0 a.docxSoftware Requirements SpecificationforProjectVersion 1.0 a.docx
Software Requirements SpecificationforProjectVersion 1.0 a.docxwhitneyleman54422
 
Role of an Architect in Software Usability Engineering
Role of an Architect in Software Usability EngineeringRole of an Architect in Software Usability Engineering
Role of an Architect in Software Usability Engineeringthinakes
 
software requirement
software requirementsoftware requirement
software requirementahmed zewita
 
Software engineering practical
Software engineering practicalSoftware engineering practical
Software engineering practicalNitesh Dubey
 
How Custom Software Development is Transforming the Traditional Business Prac...
How Custom Software Development is Transforming the Traditional Business Prac...How Custom Software Development is Transforming the Traditional Business Prac...
How Custom Software Development is Transforming the Traditional Business Prac...christiemarie4
 
Software design presentation
Software design presentationSoftware design presentation
Software design presentationbit allahabad
 
Usability principles 1
Usability principles 1Usability principles 1
Usability principles 1Sameer Chavan
 
Software Development Methodologies.pptx
Software Development Methodologies.pptxSoftware Development Methodologies.pptx
Software Development Methodologies.pptxMohamedElshaikh10
 
User Experience Distilled
User Experience DistilledUser Experience Distilled
User Experience DistilledHindu Dharma
 

Similar a Fs (20)

Design submission template
Design submission templateDesign submission template
Design submission template
 
400-600 wordsAPA format with referencesOne of the first ta.docx
400-600 wordsAPA format with referencesOne of the first ta.docx400-600 wordsAPA format with referencesOne of the first ta.docx
400-600 wordsAPA format with referencesOne of the first ta.docx
 
Software Requirements SpecificationforProjectVersion.docx
Software Requirements SpecificationforProjectVersion.docxSoftware Requirements SpecificationforProjectVersion.docx
Software Requirements SpecificationforProjectVersion.docx
 
cheatsheet.pdf
cheatsheet.pdfcheatsheet.pdf
cheatsheet.pdf
 
Lecture 5 defining the system
Lecture 5 defining the systemLecture 5 defining the system
Lecture 5 defining the system
 
Notes on software engineering
Notes on software engineeringNotes on software engineering
Notes on software engineering
 
job job
job jobjob job
job job
 
Sad presentation
Sad presentationSad presentation
Sad presentation
 
UI architecture & designing
UI architecture & designingUI architecture & designing
UI architecture & designing
 
Requirement Engineering Processes & Eliciting Requirement
Requirement Engineering Processes & Eliciting Requirement Requirement Engineering Processes & Eliciting Requirement
Requirement Engineering Processes & Eliciting Requirement
 
Software Requirements SpecificationforProjectVersion 1.0 a.docx
Software Requirements SpecificationforProjectVersion 1.0 a.docxSoftware Requirements SpecificationforProjectVersion 1.0 a.docx
Software Requirements SpecificationforProjectVersion 1.0 a.docx
 
Role of an Architect in Software Usability Engineering
Role of an Architect in Software Usability EngineeringRole of an Architect in Software Usability Engineering
Role of an Architect in Software Usability Engineering
 
software requirement
software requirementsoftware requirement
software requirement
 
Software engineering practical
Software engineering practicalSoftware engineering practical
Software engineering practical
 
How Custom Software Development is Transforming the Traditional Business Prac...
How Custom Software Development is Transforming the Traditional Business Prac...How Custom Software Development is Transforming the Traditional Business Prac...
How Custom Software Development is Transforming the Traditional Business Prac...
 
Software design presentation
Software design presentationSoftware design presentation
Software design presentation
 
Usability principles 1
Usability principles 1Usability principles 1
Usability principles 1
 
Software Development Methodologies.pptx
Software Development Methodologies.pptxSoftware Development Methodologies.pptx
Software Development Methodologies.pptx
 
Enter the Big Picture
Enter the Big PictureEnter the Big Picture
Enter the Big Picture
 
User Experience Distilled
User Experience DistilledUser Experience Distilled
User Experience Distilled
 

Más de Sutharsan nagarajan (14)

Fresher eee
Fresher eeeFresher eee
Fresher eee
 
Xampp11
Xampp11Xampp11
Xampp11
 
Xampp
XamppXampp
Xampp
 
Hotshoe
HotshoeHotshoe
Hotshoe
 
Personal
PersonalPersonal
Personal
 
Fresher it-2009
Fresher it-2009Fresher it-2009
Fresher it-2009
 
Functional spec
Functional specFunctional spec
Functional spec
 
Fs1
Fs1Fs1
Fs1
 
Sql Tags
Sql TagsSql Tags
Sql Tags
 
Hotdance
HotdanceHotdance
Hotdance
 
Wp Tech
Wp TechWp Tech
Wp Tech
 
Web 2 0
Web 2 0Web 2 0
Web 2 0
 
Wordpress
WordpressWordpress
Wordpress
 
Web 2 0
Web 2 0Web 2 0
Web 2 0
 

Fs

  • 1. Functional specification: A functional specification (or sometimes functional specifications) is a formal document  used to describe in detail for software developers a product's intended capabilities, appearance, and  interactions with users. The functional specification is a kind of guideline and continuing reference  point as the developers write the programming code. (At least one major product development group  used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for  a word processing system, then declared that the user's guide was the functional specification. The  developers were challenged to create a product that matched what the user's guide described.)  Typically, the functional specification for an application program with a series of interactive  windows and dialogs with a user would show the visual appearance of the user interface and  describe each of the possible user input actions and the program response actions. A functional  specification may also contain formal descriptions of user tasks, dependencies on other products,  and usability criteria. Many companies have a guide for developers that describes what topics any  product's functional specification should contain.  For a sense of where the functional specification fits into the development process, here are a  typical series of steps in developing a software product:  • Requirements. This is a formal statement of what the product planners informed by their  knowledge of the marketplace and specific input from existing or potential customers believe  is needed for a new product or a new version of an existing product. Requirements are  usually expressed in terms of narrative statements and in a relatively general way.  • Objectives. Objectives are written by product designers in response to the Requirements.  They describe in a more specific way what the product will look like. Objectives may  describe architectures, protocols, and standards to which the product will conform.  Measurable objectives are those that set some criteria by which the end product can be  judged. Measurability can be in terms of some index of customer satisfaction or in terms of  capabilities and task times. Objectives must recognize time and resource constraints. The  development schedule is often part or a corollary of the Objectives.  • Functional specification. The functional specification (usually functional spec or just spec  for short) is the formal response to the objectives. It describes all external user and  programming interfaces that the product must support.  • Design change requests. Throughout the development process, as the need for change to the  functional specification is recognized, a formal change is described in a design change  request.  • Logic specification. The structure of the programming (for example, major groups of code  modules that support a similar function), individual code modules and their relationships,  and the data parameters that they pass to each other may be described in a formal document  called a logic specification. The logic specification describes internal interfaces and is for  use only by the developers, testers, and, later, to some extent, the programmers that service  the product and provide code fixes to the field.  • User documentation. In general, all of the preceding documents (except the logic  specification) are used as source material for the technical manuals and online information  (such as help pages) that are prepared for the product's users. 
  • 2. • Test plan. Most development groups have a formal test plan that describes test cases that  will exercise the programming that is written. Testing is done at the module (or unit) level, at  the component level, and at the system level in context with other products. This can be  thought of as alpha testing. The plan may also allow for beta test. Some companies provide  an early version of the product to a selected group of customers for testing in a "real world"  situation.  • The final product. Ideally, the final product is a complete implementation of the functional  specification and design change requests, some of which may result from formal testing and  beta testing.  The cycle is then repeated for the next version of the product, beginning with a new  Requirements statement, which ideally uses feedback from customers about the current product to  determine what customers need or want next.  Most software makers adhere to a formal development process similar to the one described  above. The hardware development process is similar but includes some additional considerations for  the outsourcing of parts and verification of the manufacturing process itself.