Spelling suggestions: "subject:"systemutveckling"" "subject:"isystemutveckling""
1 |
Meta - method for method configuration : a rational unified process case /Karlsson, Fredrik, January 2002 (has links)
Lic.-avh. Linköping : Univ.
|
2 |
A fault classification approach to software process improvement /Henningsson, Kennet, January 2005 (has links)
Lic.-avh. Ronneby : Blekinge tekn. högsk., 2005.
|
3 |
Towards an ontology development methodology for small and medium-sized enterprises /Öhgren, Annika, January 2009 (has links)
Licentiatavhandling Linköping : Linköpings universitet, 2009.
|
4 |
Analys, design och konstruktion av en prototyp för hantering av elevdataSäll, Tommy January 2002 (has links)
No description available.
|
5 |
Quality assurance in software development & evaluation of existing quality systemsKristensson, David January 2004 (has links)
No description available.
|
6 |
Software code quality with UML-based design modelsEkberg, Linda January 2004 (has links)
No description available.
|
7 |
Requirements engineering : elicitation techniquesGunda, Sai Ganesh January 2008 (has links)
<p>Requirement engineering is the first and crucial phase in the development of software. The main aim of the requirement engineering process is gathering of requirements. It involves set of activities like system feasibility study, elicitation analysis, validation and management of the requirements. There are many methods already exist to perform the requirement gathering process and the software developers apply them to gather the requirements but still they are facing so many problems in gathering the requirements due to the lack of knowledge on result of the methods and selection of appropriate method. This affects the quality of software and increases the production cost of software. this paper presents the literature study and the experimental case study on analyzing and compare different methods for requirement gathering process, this provides the flexibility to requirements engineers to know the characteristics and the effectiveness of every method, it is useful to select the particular elicitation method depends on the type of application and the situation. And this analysis may be useful for the future development of new methods for requirement elicitation.</p>
|
8 |
Analys, design och konstruktion av en prototyp för hantering av elevdataSäll, Tommy January 2002 (has links)
No description available.
|
9 |
Quality assurance in software development & evaluation of existing quality systemsKristensson, David January 2004 (has links)
No description available.
|
10 |
Software code quality with UML-based design modelsEkberg, Linda January 2004 (has links)
No description available.
|
Page generated in 0.1109 seconds