IN4MATX 43 Lecture Notes - Lecture 7: Software Architecture, Software Architect, Hypertext Transfer Protocol
27 Apr 2018
School
Department
Course
Professor
IN4MATX – 36900 – Intro to Software Engineering
Week 4 – Lecture 7 – Architecture
Software Architecture
• An analogy to building architectures
o Parallels
▪ Design before build
▪ Satisfaction of customer’s needs
• Need to keep their customer’s needs in mind
▪ Specialization of labor
• People have different skills and are needed at different times
in the project
▪ Multiple perspectives of the final product
• A blueprint isn’t the only perspective; could have artist
renderings or 3d models
o Same goes with software; it’s not just represented by
code
o Might be represented by use cases or user interface
mockups
▪ Intermediate points where plans and progress are reviewed
• To make sure you are on the right path that the customer
intends
o The architect
▪ A distinctive role and character in a project
• Promotes the integrity of the project
▪ Broad training
• Worked on a lot of systems
▪ Extensive experience
▪ Deep understanding of the domain
• Understands the processes and different systems out there
▪ Leads the team
• Represent the development team to the customers and
stakeholders
▪ Good communicator
▪ Decision maker
▪ Deals with a high level of abstraction than those performing
construction
• At a higher level than the people who actually build it
• A more conceptual level for the project’s structure
▪ Often serves as the interface to key business
stakeholders/customers
o Litations of analogy
find more resources at oneclass.com
find more resources at oneclass.com
