software architecture

A software system’s architecture should be a composition and interplay

of different elements like:
• Processing
• Data, also referred as information or state
• Interaction
Building blocks of software architecture
• There are three building blocks of Software architecture

• Components
• Connectors
• Configurations
 Components

• Elements that encapsulate processing and data in a system’s

architecture are referred to as software components. A software
component is an architectural entity that:
• encapsulates a subset of the system’s functionality and/or data
• restricts access to that subset via an explicitly defined interface
• has explicitly defined dependencies on its required execution context
• The components typically provide application-specific services. A
component may be simple or composite. Composite components can
be described a system.
 Connectors
• In complex systems interaction may become more important and challenging than the
functionality of the individual components. Connectors typically provide application-independent
interaction facilities. A connector is an architectural element that models
• interactions among components
• rules that govern those interactions

• Simple interactions
• procedure calls
• shared variable access

• Complex and semantically rich interactions

• client-server protocols
• database access protocols
• piped data streams
Configurations

• Components and connectors are composed in a specific way in a

given system’s architecture to accomplish that system’s objective. An
architectural configuration or topology
• is a set of specific associations between the components and connectors of a
software system’s architecture
• is represented by connected graph of components and connectors
• describes architectural structure
Software Estimation Techniques
• There are different Software Testing Estimation Techniques which can
be used for estimating a task.
• Delphi Technique
• Work Breakdown Structure (WBS)
• Three Point Estimation
• Functional Point Method
Delphi technique
• Delphi technique – This is one of the widely used software testing
estimation technique.
• In the Delphi Method is based on surveys and basically collects the
information from participants who are experts.
• In this estimation technique each task is assigned to each team
member & over multiple rounds surveys are conduct unless & until a
final estimation of task is not finalized.
• In each round the thought about task are gathered & feedback is
provided. By using this method, you can get quantitative and
qualitative results
Work Breakdown Structure (WBS)

• A big project is made manageable by first breaking it down into

individual components in a hierarchical structure, known as the Work
breakdown structure, or the WBS.
Three Point Estimation

• Three point estimation is the estimation method is based on statistical

data.
• It is very much similar to WBS technique, task are broken down into
subtasks & three types of estimation are done on this sub pieces.
 Functional Point
• Functional Point is measured from a functional, or user, point of view.
• It is independent of computer language, capability, technology or
development methodology of the team.
• It is based on available documents like SRS, Design etc.
• In this FP technique we have to give weightage to each functional
point. Prior to start actual estimating tasks functional points are
divided into three groups like Complex, Medium & Simple. Based on
similar projects & Organization standards we have to define estimate
per function points.