Genomförbarhet aka .
Feasibility – the measure of how beneﬁcial or
practical an information system will be to an
Feasibility analysis – the process by which feasibility
Operational feasibility – a measure of how well a solution will
work or be accepted in an organization.
Preformance. Does the system provide adequate throughput and response time?
Information. Does the system provide end-users and managers with timely, accurate usefully formatted information
Economy. Does the system offer an adequate service to reduce cost and increase profits
Control. Adequate protection and accuracy of information
Efficiency. Maximum use of resources, and minimum delays
Services. Desirable and reliable service and flexible and expandable
Technical feasibility – a measure of the practicality of a
technical solution and the availability of technical resources
Schedule feasibility – a measure of how reasonable the
project timetable is.
Economic feasibility - a measure of the cost-effectiveness of
a project or solution.
Kravanalys syftar till att översätta verksamhetsbehov till systemkrav.
Funktionella krav: Funktionalitet, användbarhet, supportbarhet
Icke-funktionella krav: designbegränsningar, implementationskrav, Interfacekrav, fysiska krav
Prioritering av krav
Kravanalys - processen
• Syfte med processen är att:
• studera användarnas behov av ett system
• ta fram en modell av användarnas krav
• beskriva modellen i kravdokumentet
• Denna process sker interaktivt (mellan olika grupper av användare/intressenter
och design-teamet) .En 6-steg process
• 1. Samla
• 2. Klassiﬁcera
• 3. Lös motsägelser
• 4. Prioritera
• 5. Validera
• 6. Förstå tillämpning
10. Look and Feel Requirements
11. Usability and Humanity Requirements
12. Performance Requirements
13. Operational and Environmental Requirements
14. Maintainability and Support Requirements
15. Security Requirements
16. Cultural and Political Requirements
17. Legal Requirements
Functional requirements may be calculations, technical details, data manipulation and processing and other specific functionality that define what a
system is supposed to accomplish.
6. The Scope of the Work
7. Business Data Model
8. The Scope of the Product
9. Functional Requirements
- For ease of use, we have found it convenient to think of requirements as belonging to a type.
- Functional requirements are the fundamental or essential subject matter of the product. They
describe what the product has to do or what processing actions it is to take.
- Nonfunctional requirements are the properties that the functions must have, such as performance
and usability. Do not be deterred by the unfortunate type name (we use it because it is the most
common way of referring to these types of requirements). These requirements are as important as the
functional requirements for the product's success.
- Project constraints are restrictions on the product due to the budget or the time available to build
- Design constraints impose restrictions on how the product must be designed. For example, it might
have to be implemented in the hand-held device being given to major customers, or it might have to
use the existing servers and desktop computers, or any other hardware, software, or business
- Project drivers are the business-related forces. For example, the purpose of the project is a project
driver, as are all of the stakeholders-each for different reasons.
- Project issues define the conditions under which the project will be done. Our reason for including
them as part of the requirements is to present a coherent picture of all factors that contribute to the
success or failure of the project and to illustrate how managers can use requirements as input when
managing a project.