Sciweavers

Free Online Productivity Tools i2Speak i2Symbol i2OCR iTex2Img iWeb2Print iWeb2Shot i2Type iPdf2Split iPdf2Merge i2Bopomofo i2Arabic i2Style i2Image i2PDF iLatex2Rtf Sci2ools

19

ICSE
2003
IEEE-ACM

favoriteEmaildiscussreport

192views Software Engineering» more ICSE 2003»

Architectural Requirements Engineering: Theory vs. Practice

13 years 10 months ago

Architectural Requirements Engineering: Theory vs. Practice

Download se.uwaterloo.ca

This paper discusses how architectural requirements engineering fits into an overall software development process in the concept and definition phases of a project. It defines a reference process identifying the “ideal” artifacts and their interrelationships, describes some key technical activities that are useful for producing these artifacts, and captures some practical experience in commercial projects.

Robert W. Schwanke

Real-time Traffic

Architectural Requirements Engineering | ICSE 2003 | Key Technical Activities | Software Development Process | Software Engineering |

claim paper

Related Content

» The Engineering of a Compression Boosting Library Theory vs Practice in BWT Compression

» Flow engineering for physical implementation theory and practice

» Engineering a Distributed eVoting System Architecture Meeting Critical Requirements

» Language communities in enterprise architecture research

» Information Flow Between Requirement Artifacts Results of an Empirical Study

» Activity Theory a Framework to Software Requirements Elicitation

» Fourth international workshop on sharing and reusing architectural knowledge SHARK 2009

» Separation in Theory Coordination in Practice

» Language Engineering in Practice

Post Info
More Details (n/a)

Added	07 Jul 2010
Updated	07 Jul 2010
Type	Conference
Year	2003
Where	ICSE
Authors	Robert W. Schwanke

Comments (0)