1981
DOI: 10.1109/tse.1981.234533
|View full text |Cite
|
Sign up to set email alerts
|

Major Issues in Software Engineering Project Management

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
21
0

Year Published

1984
1984
2010
2010

Publication Types

Select...
5
4

Relationship

0
9

Authors

Journals

citations
Cited by 44 publications
(21 citation statements)
references
References 6 publications
0
21
0
Order By: Relevance
“…Finally, hear she often crafts a design for the program before generating the code, documents the program fully, and writes the program in a structured, modular fashion so that others can easily read and modify it. Major issues in software engineering at high sublevels within this level of expertise are discussed by Thayer, Pyster and Wood (1981).…”
Section: Level IV Software Developermentioning
confidence: 99%
“…Finally, hear she often crafts a design for the program before generating the code, documents the program fully, and writes the program in a structured, modular fashion so that others can easily read and modify it. Major issues in software engineering at high sublevels within this level of expertise are discussed by Thayer, Pyster and Wood (1981).…”
Section: Level IV Software Developermentioning
confidence: 99%
“…Moreover, unique tools and techniques were developed to address challenges related to management of software development projects [3], [4], [5]. Many investments have been especially directed to support project upfront planning activities, in particular to find reliable duration, effort and cost estimation models for project outcome prediction.…”
Section: Introductionmentioning
confidence: 99%
“…The iterative life cycle model that has become a standard in the software industry lead by Rational Unified Process (RUP), where on behalf the waterfall process, the iterative approach is superior providing a mature, rigorous, and flexible software engineering process (Kruchten, 2000). On the other hand, the requirements prototyping model aims to build a partial implementation of a the system, where the main focus is to express purpose of learning about the system's requirements and capture what was learned when working with the prototype and then use it in documenting the actual requirements' specifications for the real system development (Thayer, 2000). Both models allowed us to construct a prototype in few weeks (four weeks in total).…”
Section: Methodsmentioning
confidence: 99%