Win a copy of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) this week in the OCAJP forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

about project architecture

 
shruti patel
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
what is project architecture?give brief explanation about
project architecture?
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Why do you ask? Where did you hear/read this term?
 
shruti patel
Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i was asked this question in interview and i answered the tier which is used in our project.
but still i need more information about this.
 
Jesper de Jong
Java Cowboy
Saloon Keeper
Pie
Posts: 15435
41
Android IntelliJ IDE Java Scala Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Doesn't sound like this belongs in the "IDEs, Version Control and other tools" forum. I am moving it to a more appropriate forum; please follow the link at the top of the post to continue the discussion.
 
lenin rajavel
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by shruti patel:
what is project architecture?give brief explanation about
project architecture?


i guess you have asked about software architecture.

Whenever you are into a new development project people in the top level will show some diagrams with box and line notations and say that's the architecture of the system.After that everyone will forget that.

There is 'n' number of definitions for software architecture. But from my opinion software architecture is the communication of explicit and documented design decisions to solve particular set of business goals.it consists the structure,collaboration and dynamics of the system. Moreover it is the identification and resolution of non functional requirements in the presence of functional requirements. These are known as the "ilities" of the system. These quality attributes are such as availability, performance,modifiability,security,testability,usabilty etc...

The best thing about software architecture is we can have it before the actual system is built. so you can validate it before implementing it by using ATAM or some other technique so that you can avoid many risks.

But there's slight difference between software architecture and system architecture.

Hope i have clarified something.

Thanks

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic