Skip to main content


Showing posts from October, 2015

Visualizing the state of projects using geometric figures (follow-up)

Building a project status spectrum

In the previous post entitled "Visualizing the state of projects using geometric figures", it's possible to build a status spectrum for on-going projects with respect to time.

Framework: Define a set of variables: scope, time, budget, priority...Choose a chart in which to display the variables. The chart has to represent all variables. Each variable has a label and a value associate with it.For homogeneity reasons, each value should normalized in order to fit a predefined range. In this context the only fixed elements are the chart and labels of the variables. All the other elements vary with time.

T(1):Chart(1), T(2):Chart(2), T(3):Chart(3),...,T(n):Chart(n)

The "SUM" of all charts on the same timeline is the spectrum.
A predefined finite timeline and variables represents the time frame of a project.An infinite timeline with finite variable represents an on-going project.An infinite timeline with infinite variables repres…

Sizing Software Applications

Applications are software programs designed to perform functions for users. They use operating system services and other supporting programs to perform a designated function.
Before developing an application, it would be nice to have an estimate of its size in terms of effort and/or costs.
Applications can be big and complex or small and simple. An application that needs to interface and interact with users can be characterized by a certain number of elements, such as wireframes, use cases, business rules, data tables, reports, and correspondences. The size of an application can be determined by the number of these elements. The table below describes a hypothetical example.

Application Number of Elements Wireframes Use Cases Business Rules Data Tables Reports Correspondences 10 50 90 100 10 15 Estimated effort to develop one element of simple complexity level in man-days 3 5