WEB DEVELOPMENT
Works
Please wait
Prices
Please wait
About us
Please wait
Technical task
Technical task for software development (IEEE 830 is a standard recommended structure)
- Introduction
- GoalShort description of what needs to be developed
- DefinitionsA list of specific terms essentially important for clear understanding of the task, for example, «Maps» which is an external plugin of Google maps.
- Core audience and project scopeAudience for which a project is intended. For example, tic-tac-toe game for school-aged children all over the world.
- LinksLinks to resources used as samples for development, technical guides, laws, standards, etc. with a short description. For example, HTML coding compliant to https://www.w3.org/TR/html5/
- Goal
- General description
- Product review
- Product functionalityA list of performance capabilities provided by product from the user's point of view.
- Users classificationFor example, a project administrator, chat moderator, visitor
- Product operational environment For example, a server needs PHP, MySQL, a client needs correct display in browsers Internet Explorer 9 and later, WebKit, Opera, and also fully responsive design and correct display on mobile devices
- Restrictions, rules and standardsFor example, a website must meet security demands, object-orientable code with comments.
- User documentationWhat user documentation is developed
- Assumptions and dependenciesFor example, it is supposed that a server must be in function not less than 98% of time
- Product scope
- Functional block NThere can be several blocks like this, for sites they are usually divided into pages and popup dialogs
- Description and priorityDetailed textual and graphic description of an application element
- Сause-and-effect connections, algorithms (processes movement, workflows)Detailed description of this application element functioning
- Functional requirementsDescription of functions which must be performed by this element (for example to send email with an order)
- Description and priority
- Functional block N
- External interface requirements
- User interfacesGraphic or textual description of pages, forms and dialogues which are seen by visitors of the website.
- Program interfacesFor example, description of interaction interface with API web application
- Hardware interfacesIt can be of importance for the website what hardware input devices are used, for example, mouse/touchpad.
- Communication interfacesFor example, an application interacts with a server by TCP/IP protocol in asynchronous mode (REST)
- User interfaces
- Nonfunctional requirements
- Performance requirements
- Data security requirementsRequirements for stored data validity and for its access restriction by unauthorized persons.
- Software quality criteria
- System safety requirementsFor example, a system must be resistant to XSS attacks and exploits deployment
- Other requirements
- Annex A: Glossary
- Annex B: Processes models and application environment, and other charts
- Annex C: Key objectives list
Contacts
Please wait
Please wait