| |
SOFTWARE
ARCHITECTURE |
|
| |
We
can compare ourselves with typical architects of construction
trade. |
|
| |
Structures
can be assembled with sticks and stones or computer software
and hardware, but the role of the architect remains the
same. |
|
| |
Architects
spend the lion's share of their time up front: listening
to clients, understanding the totality of their needs and
resources, scrutinizing feasibility, forming a practical
vision of a structure, and creating a blueprint. As the
structure is built, the architect intervenes in the client's
favor, ensuring compliance to the plan and guiding the vision
through the tempest of design changes, crises and ambiguities.
Client advocacy is the cornerstone of the architect's role.
|
|
| |
A
lifelong mason, no matter how talented, cannot necessarily
fill the role of an architect. If you have a chisel, everything
tends to look like a rock. |
|
| |
We
at Bean Architects intend to collaborate with clients organization
to clearly identify the benefits of adapting software architecture
approach and culminate with detailed requirements for a
technology solution to realize the benefits of an effective
IT strategy built around sound business model. |
|
| |
|
|
| |
........................................................................................................................................... |
|
| |
Architecting
IT Process |
|
| |
Every
business is a blend of processes that must work in tandem
for overall success. With companies getting larger and more
fragmented in a distributed business space, the glue that
binds them is information. Hence, Information systems that
underlie each process must all "talk" to each
other seamlessly to achieve the business goals. We at Bean
Architects, architect information systems with sound foundation
to enable companies to effectively synchronize business
processes and information systems to optimize the operational
efficiencies. |
|
| |
|
|
| |
|
|
| |
........................................................................................................................................... |
|
| |
Software
Architecture - A Structured Approach |
|
| |
Software
Architecture and Re-engineering of applications can be achieved
with a well-architected approach. An effective architecture
aligns the technology to the business, ensures that the
various components of the application work cohesively, and
provides a road map for its implementation. |
|
| |
We,
at Bean Architects provide services in phases as discussed
below. |
|
| |
........................................................................................................................................... |
|
| |
Pre-Design
Phase |
|
| |
We
listen to understand the scope of the project, the client's
key design points, requirements, and expectations. We also
study the context of the project - the entire enterprise
of which the project is a part. A design direction begins
to take shape, with the architect and client, collaborating
and refining their understanding until a shared vision emerges. |
|
| |
........................................................................................................................................... |
|
| |
Domain
Analysis Phase |
|
| |
We
undertake to thoroughly understand and document the areas
(domains) for which the system will be built and to learn
the client requirements in detail. The desired behaviors
of the system are outlined. We assess the client's business
and technology environment, the interplay and define the
scope of work. |
|
| |
........................................................................................................................................... |
|
| |
Schematic
design Phase |
|
| |
Architectural-level
designs depicting the domain characteristics and technology
structure are prepared. The look and feel of the system
- user interface style - is designed. Prototypes are built
at this point, if they are needed. Migration and risk assessments
are performed. |
|
| |
We
continue to extend the design with detailed requirements
and ensure comprehensive view of the system to be developed.
The client validates to see that all the stated requirements
are considered. Subsequently system design and its details
are documented. |
|
| |
|
|
| |
........................................................................................................................................... |
|
| |
Project
Document Phase |
|
| |
Focusing
on the requirements of system development team, the construction
process, the roles of the team members, and the construction
sequences are documented. The construction guide , user
interface style guide , and test guides are identified.
The document also highlights the technology tools to be
used and the methodologies to be implemented during construction
of the system. |
|
| |
........................................................................................................................................... |
|
| |
Staffing
and Contracting Phase |
|
| |
We
assist in identifying the system development team according
to the defined technology requirements. For projects that
are outsourced, tenders are submitted to vendors and potential
vendor is evaluated. |
|
| |
........................................................................................................................................... |
|
| |
Construction
Phase |
|
| |
We
assume a supervisory role during construction ensuring that
the client's requirements are understood and executed. We
conduct design reviews and analyze problems and change requests.
We help in incorporating the accepted change in exiting
design by assessing the impact on overall design and cost.
|
|
| |
Post
Construction Phase |
|
| |
We
supplement our services by training the end users on the
use of the system built. |
|
| |
|
|
| |
........................................................................................................................................... |
|
| |
|
|
