Software architecture is about change.
All software systems must evolve to meet the ever-expanding needs of its
users.
It is vital for organizations to perform software maintenance in such a
way as to reduce complications arising from changes and the potential
for new bugs to be introduced by the change.
We need a comprehensive solution that helps us understand changes and
their impact.
Also there is late-lifecycle changes which are changes that occur after
at least one cycle of the development process has been completed and a
working version of the system exists.
These unavoidable changes pose an especially high risk for developers.
Understanding late-lifecycle changes is important because of their high
cost, both in money and effort, especially when they are due to
requirements changes.
Furthermore, these late-lifecycle changes tend to be the most crucial
changes because they are the result of better understood customer and
end-user needs.
All the best
Ashraf Galal
Muhammad Waseem wrote:
>
> Hi all
> I am new on software architecture, any one likes to explain about what
> called software architecture change?
> I am thinking adding, deleting merging and splitting in packages or
> name space called software architecture change?
> What you people think?
>
> Muhammad Waseem
>
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/service-orientated-architecture/join
(Yahoo! ID required)
<*> To change settings via email:
[email protected]
[email protected]
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
