Lupedigital Software has a proven track record of providing custom application development and maintenance services to its clients in various industries, with the ability to handle large enterprise systems and provide cost effective on time support.

We provide both end-to-end solutions - from requirements gathering to application maintenance - and specific design and development expertise. We're the expert users of various software platforms such as Visual Studio (.NET), Visual Age (Java Development tool from IBM), etc. Our teams employ industry standard tools, such as Rational Rose and Designer 2000, and techniques during the software development life cycle.

The Lupedigital Software development teams have the ability to understand the business processes and record them using our own Software Requirement Specification template by utilizing the end user interview process. Once the requirements are defined, they get passed to an independent inspection team for detailed review.

Component Reusability
Component Reusability is about building a library of frequently used components, thus allowing new programs to be assembled quickly from existing components. Component Reusability has produced greater schedule and effort savings than any other practice. We have applied this concept not only to the code, but also to the design, data, documentation, test materials, specifications, and plan.

We have created a repository named ‘Component Repository’ to store the components that are identified as commonly used components. Currently this repository stores more than 100 reusable components. The repository has a search feature to look for similar components.

The repository is managed by the Reuse Group, which has members from the design as well as development team. This is a part of our long-term strategy.

Control Board
On moderate to very large projects, a central control mechanism is needed to ensure that every change is properly considered and coordinated. That’s why on such projects, we establish a Change Control Board. It includes the members from design, development, and test teams. It also sometimes includes the members from the customer team.

Risk Assessment
• Risk Identification: The first step in producing the Top-10 Risks list is to identify the factors that pose a risk to the project schedule. For example, a potential risk with respect to requirement is that ‘Requirements have been baselined but continue to change’ or ‘Vaguely defined areas of the application are more time-consuming than expected’.

Risk Analysis: The next step is to assess the likelihood and impact of each risk and the risk levels of alternate practices. A useful risk analysis practice is to determine the “risk exposure” of each identified risk. Risk exposure is equal to the probability of the unexpected loss multiplied by the size of the loss. For example, if there is a 25% chance that it will take 4 weeks longer to get the project approved, then the risk exposure is 1 week.