Scribd
Upload
51 views2 pages

Az 809

Litware is an ISV with a monolithic retirement fund management system built on ASP.NET and C#. The system has over 80 code branches across its offices. Merging changes takes months and introduces bugs. Litware plans new investment planning apps with minor integration to the existing system. It also wants to improve agility, extract shared code to packages, and use cloud services. The new apps must minimize firewall access, use least privilege permissions, support isolated development branching, and allow package creation and permissions editing by team leaders.

Uploaded by

Sahitram Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
51 views2 pages

Az 809

Litware is an ISV with a monolithic retirement fund management system built on ASP.NET and C#. The system has over 80 code branches across its offices. Merging changes takes months and introduces bugs. Litware plans new investment planning apps with minor integration to the existing system. It also wants to improve agility, extract shared code to packages, and use cloud services. The new apps must minimize firewall access, use least privilege permissions, support isolated development branching, and allow package creation and permissions editing by team leaders.

Uploaded by

Sahitram Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

.

 Topic 1, Litware inc. Case Study: 1


Overview

Existing Environment

Litware, Inc. an independent software vendor (ISV) Litware has a main office and five branch
offices.

Application Architecture

The company’ s primary application is a single monolithic retirement fund management


system based on ASP.NE T web forms that use logic written in V8.NET. Some new sections
of the application are written in C#.
Variations of the application are created for individual customers. Currently, there are more
than 80 have code branches in the application’s code base.
The application was developed by using Microsoft Visual Studio. Source code is stored in
Team Foundation Server (TFS) in the main office. The branch offices access of the source
code by using TFS proxy servers.
Architectural Issues

Litware focuses on writing new code for customers. No resources are provided to refactor or
remove existing code. Changes to the code base take a long time, AS dependencies are not
obvious to individual developers.

Merge operations of the code often take months and involve many developers. Code merging
frequently introduces bugs that are difficult to locate and resolve.

Customers report that ownership costs of the retirement fund management system increase
continually. The need to merge unrelated code makes even minor code changes expensive.
Requirements

Planned Changes

Litware plans to develop a new suite of applications for investment planning. The investment
planning Applications will require only minor integration with the easting retirement fund
management system.

The investment planning applications suite will include one multi-tier web application and
two iOS mobile applications. One mobile application will be used by employees; the other will
be used by customers.

Litware plans to move to a more agile development methodology. Shared code will be
extracted into a series of package.

Litware has started an internal cloud transformation process and plans to use cloud based
services whenever suitable.

Litware wants to become proactive m detecting failures, rather than always waning for
customer bug reports.
Technical Requirements

The company's investment planning applications suite must meet the following technical
requirements:
• New incoming connections through the firewall must be minimized.

• Members of a group named Developers must be able to install packages.

• The principle of least privilege must be used for all permission assignments

• A branching strategy that supports developing new functionality in isolation must be used.

• Members of a group named Team leaders must be able to create new packages and edit the
permissions of package feeds

You might also like