Tailoring Architecture Centric Design Method with Rapid Prototyping
Nitish M. Devadiga

TL;DR
This paper enhances the architecture centric development method by integrating rapid prototyping to improve early-stage design, requirement transition, and reduce iteration cycles, thereby aligning systemic properties with stakeholder needs.
Contribution
It introduces a customized architecture centric development method that incorporates rapid prototyping to facilitate early requirement elicitation and design evaluation.
Findings
Reduced number of iterations in architectural design process
Improved transition of requirements into architectural solutions
Enhanced stakeholder feedback and risk mitigation
Abstract
Many engineering processes exist in the industry, text books and international standards. However, in practice rarely any of the processes are followed consistently and literally. It is observed across industries the processes are altered based on the requirements of the projects. Two features commonly lacking from many engineering processes are, 1) the formal capacity to rapidly develop prototypes in the rudimentary stage of the project, 2) transitioning of requirements into architectural designs, when and how to evaluate designs and how to use the throw away prototypes throughout the system lifecycle. Prototypes are useful for eliciting requirements, generating customer feedback and identifying, examining or mitigating risks in a project where the product concept is at a cutting edge or not fully perceived. Apart from the work that the product is intended to do, systemic properties…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
