Question

Sub : Software Oriented System

Situation like that client (TD Bank) come with us (IT/We developer) for developing new wesite

here new website meaning that creating website first time.

You must produced 2 models

1) Resuse component model

2) component model

Client come with us for making nee website for first time

Answer 1

As it is known that banking system is very secure system so we have to make the website very carefully using secure systems.

We will prefer here the component model and will later on resue the component model as clinet is coming with us for the first time.

So there are differnt uses of using the component model here :

1.It allows for Resue - Components are atomic units, and building with components allows for their reuse in future development cycles. Since technologies come and go, this is invaluable. If you build your application in a componentized format, you’re able to swap the best components in and out.

2.A Component-based UI Approach Accelerates Development -Using a component-based UI approach supports iterative, agile development. Components are hosted in a library from which teams can access, integrate and modify them throughout the development process.

3.It Ensures User Experience Consistency Across a Portfolio-The component library acts as a point of governance for the business, designers, and quality assurance teams. In the case of Quality Assurance (QA), teams often have challenges validating the user interface due to a lack of an approved set of user interface standards. The component-based approach enables the creation of a library that provides that approved reference point. This enables the QA team to govern the compliance to UX standards across a portfolio of applications.

4.It Easily Integrates into the Development Process-As components are created, production quality user interface code is managed within a source code repository such as GitHub. Application development teams are well versed in using source code repositories, and so they are able to extract the code as needed and incorporate it into the application. Leveraging the initial component as a starting point, development teams can extend it to meet their needs.

5.Component-based UI Development Optimizes the Requirements & Design Process-Using the component-based library as a reference, product managers, business analysts and user experience designers can spend less time defining the detailed application functionality and user experience. As they work through the definition process and requirements elaboration, they can reference a component as the baseline for the requirement, and then only spend time defining the required extensions and business logic.

6. It Speeds Up the Transition from Design to Development-As the rate of change within businesses continues to accelerate, teams needs to find ways to accelerate the “Time to Value” for application development projects. Shifting to a design approach that demonstrates the user experience in the browser will have a significant impact on delivery timelines. There is often the issue of “lost in translation” that occurs when a wireframe or visual design is handed over to a development team for implementation. During the process of turning that into the application user interface, issues are surfaced and some portions are not translated correctly.