awareness the lack of the importance of architectural ...then there is a lack of awareness of the...
TRANSCRIPT
Awareness the Lack of the Importance of Architectural Design to Software
Development Using Software Architecture Design Process
Adluri.Vijaya Lakshmi1, Chappidi.Anjanamma
1, Dr.Katta Subba Rao
2
1Assistant Professor, Department of CSE, B.V.R.T, Narsapur. Medak Dist, Telangana-502313, India 2Professor, Department of CSE, B.V.R.I.T, Narsapur, Medak Dist, Telangana- 502313, India
ABSTRACT:
In the Software Engineering Software architecture is still an emerging discipline. Software
design provides a design plan that describes the elements of a system, how they fit, and work
together to fulfill the requirement of the system. The objectives of having a design plan are as
follows: To negotiate system requirements, and to set expectations with customers,
marketing, and management personnel. Act as a blueprint during the development process.
Guide the implementation tasks, including detailed design, coding, integration, and testing. In
the Existing System, there is no “Design Plan” that describes the elements of the system.
Then there is a lack of awareness of the importance of the architectural design to software
development. We proposed a new system, that is “Software Architecture Design Process” It
Contains some methods, these methods are used for awareness of the importance of the
architectural design to software development.
KEYWORDS:
Software Engineering, Software Architecture (SA), Design Plan, Software Architecture Design Process
1. INTRODUCTION TO SOFTWARE ARCHITECTURE DESIGN PROCESS
The architecture design process focuses on the decomposition of a system into different
components and their interactions to satisfy functional and nonfunctional requirements. The
key inputs to software architecture design are −The requirements produced by the analysis
tasks. The hardware architecture(the software architect in turn provides requirements to the
system architect, who configures the hardware architecture). The result or output of the
architecture design process is an architectural description. The Software Architecture Design
Process Contains some methods like understand the Problem, Evaluate the Architectural
Design and Transform the Architectural Design. These methods are used for the “Design
Plan” for the Software Architectural Design.
2. No “Design Plan” that describes the elements of the system (Existing System)
In this Existing System, there is no “design plan” that describes the elements of the System,
how they fit, and work together to fulfill the requirement of the system, and then there is a
lack of awareness of the importance of the architectural design to software development.
Then the goals of software architectural design are very low levels and very week for
implementation. The software architecture design in the Software Engineering is lack of
control of Interfaces are also very week Here, the overview of Software Architecture and
Design are shown in below figure.
International Journal of Scientific Research in Engineering (IJSRE)
IJSRE July, Vol (1), Issue (7) www.ijsre.in Page 1
The Uses of Software System Architecture and Design are shown in below figure:
3. Software Architecture Design Process (Proposed System)
We Proposed a Software Architecture Design Process Methods, Then the awareness of lack
of importance of software architecture design is very easy in the software development. The
basic architecture design process is composed of the following steps:
3.1 Understand the Problem
This is the most crucial step because it affects the quality of the design that follows.
Without a clear understanding of the problem, it is not possible to create an effective
solution. In fact, many software projects and products are considered as unsuccessful because
they did not actually solve a valid business problem or have a recognizable return on
investment ROI.
3.1.1 Identify Design Elements and their Relationships
In this phase, build a baseline for defining the boundaries and context of the system.
Decomposition of the system into its main components is based on the functional
International Journal of Scientific Research in Engineering (IJSRE)
IJSRE July, Vol (1), Issue (7) www.ijsre.in Page 2
requirements. The decomposition can be modeled by using a design structure matrix DSM,
which shows the dependencies between design elements without specifying the granularity of
the elements. In this step, the first validation of the architecture is done by describing a
number of system instances and this step is referred as functionality based architectural
design.
3.2 Evaluate the Architecture Design
Each quality attribute is given an estimate, so in order to gather qualitative measures or
quantitative data, the design is evaluated. It involves evaluating the architecture for
conformance to architectural quality attributes requirements. If all the estimated quality
attributes are as per the required standard, the architectural design process is finished. If not,
then the third phase of software architecture design is entered architecture transformation.
However, if the observed quality attribute does not meet its requirements, then a new design
must be created.
3.3 Transform the Architecture Design
This step is performed after an evaluation of the architectural design. The architectural design
must be changed until it completely satisfies the quality attribute requirements. It is
concerned with selecting design solutions to improve the quality attributes while preserving
the domain functionality. Further, a design is transformed by applying design operators,
styles, or patterns. For transformation, take the existing design and apply design operator
such as decomposition, replication, compression, abstraction, and resource sharing.
Moreover, the design is again evaluated and the same process is repeated multiple times if
necessary and even performed recursively. The transformations i.e. quality attribute
optimizing solutions generally improve one or some quality attributes while they affect others
negatively. Here, the above steps of Architecture Design Process is shown in the below
figure.
International Journal of Scientific Research in Engineering (IJSRE)
IJSRE July, Vol (1), Issue (7) www.ijsre.in Page 3
4. CONCLUSION:
In the Existing System, the lack of awareness of the importance of the architectural design
to software development. Then there is no “design plan” that describes the elements of the
system. We proposed a new system ,that is “Software Architecture Design Process” It
Contains some methods, these methods are used for awareness of the importance of the
architectural design to software development. These methods are Understand the Problem,
Evaluate the Architecture Design and Transform the Architecture Design These methods are
used for awareness of the importance of the architectural design to software development.
These are very good awareness methods for the software Architecture Design in the Software
Engineering.
5. REFERENCES
1. [Bosch2000] Jan Bosch: Design and Use of Software Architectures: Adopting and
Evolving a Product-Line Approach (ACM Press). 07. June 2000, Addison-Wesley
Longman, Amsterdam, 2000.
2. [Brown2015]Simon Brown: Software Architecture For Developers.
3. eBook: http://leanpub.com/software-architecture-for-developers).
4. G.Starke: Very pragmatic and practical approach to software architecture.
5. [Buschmann+1996] Frank Buschmann, Regine Meunier, Hans Rohnert, Peter
Sommerlad: A System of Patterns:Pattern-Oriented Software Architecture: 1 (Wiley
Software Patterns). 1. edition 1996, Wiley.
6. G.Starke: Most likely the most famous and groundbreaking book on architecture patterns.
7. [Rozanski+2011] Rozanski, Nick/Woods, Eoin: Software Systems Architecture -
Working with Stakeholders Using Viewpoints and Perspectives, 2nd Edition, Addison
Wesley 2011.
8. [Schmidt+2000] Douglas C. Schmidt, Michael Stal, Hans Rohnert, Frank Buschmann:
Pattern-Oriented Software Architecture: Volume 2: Patterns for Concurrent and
Networked Objects. Wiley, 2000.
9. A.Vijaya Lakshmi, Dr.K.Subba Rao Published a International Journal on” Understand
the Lack of role of software architect Using Software Architecture Expertise Areas”
International Journal of Scientific Research in Engineering(IJSRE),Vol-1,Issue-6, Page
No’s:1-4 June 2017
10. [Vernon2013]Vernon, V.: Implementing Domain Driven Design. 1st edition (Febr.
2013), Addison Wesley, p.656, 2013.
11. [Vernon2016]Vernon, V.: Domain Driven Design Distilled. Addison Wesley, 2016.
12. David Budgen. Software Design. Pearson Addison Wesley; 2nd edition (May 15, 2003).
1st Edition: 1994.
13. IEEE Recommended Practice for Software Design Descriptions, Std 1016-1998. (Local
copy)
14. IEEE Recommended Practice for Architectural Description of Software Intensive
Systems, Std 1471-2000. (Local copy)
International Journal of Scientific Research in Engineering (IJSRE)
IJSRE July, Vol (1), Issue (7) www.ijsre.in Page 4
15. Philippe Kruchten. "Architectural Blueprints -- The 4+1 View Model of Software
Architecture", IEEE Software, 12(6):42-50 (November 1995). (Local copy )
16. Mark W. Maler, David Emery, and Rich Hilliard. "Software Architecture: Introducing
IEEE Standard 1471", IEEE Computer, April 2001. (Local copy)
17. Bernd Oestereich. Developing Software with UML: Object-Oriented Analysis and Design
in Practice. Addison-Wesley Pub Co; 1st edition (March 1, 1999).
18. David Lorge Parnas. ``On the Criteria To Be Used in Decomposing Systems into
Modules. Comm. ACM 15(12):1053-1058 (Dec. 1972).
19. David Lorge Parnas and Paul C. Clements. ``A Rational Design Process: How and Why
to Fake It. IEEE Transactions on Software Engineering 12(2):251-256 (Feb. 1986)
20. Edward Yourdon and Larry L. Constantine. Structured Design: Fundamentals of a
Discipline of Computer Program and System Design. Prentice-Hall, 1979.
A classic. Selected quotes.
International Journal of Scientific Research in Engineering (IJSRE)
IJSRE July, Vol (1), Issue (7) www.ijsre.in Page 5