'Use software models' to talk to the business

Diagrams that model how a software project will work should be used to facilitate communication between the business and IT.

Diagrams that model how a software project will work should be used to facilitate communication between the business and IT.

Software models are often used in the design stage of a project to provide a visual representation of how the various component parts of an application being developed work together. The diagrams capture the flow of data across different systems.

Chris Howard, vice-president and service director at Burton Group, said, "The model provides a way to capture decision," which is important if the people responsible for a technical decision are no longer working on the project.

He urged users to treat modelling as a valuable communications tool. "Projects benefit from a model linked to the software development lifecycle," he said.

This may prove challenging warned Anne Thomas Manes, vice-president and research director at Burton Group.

She said internal software development teams had a poor attitude towards software modelling, as they generally preferred to start coding an application, rather than spend time on the model.

Instead of training end-users to understand models and getting development teams to build models, Burton Group suggested that an expert modelling team could be deployed to help train staff and develop the models required for the project. This approach is being used by the US Department of Defense.

Read article: Tetley's SAP project


Read more on Business applications

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchCIO

SearchSecurity

SearchNetworking

SearchDataCenter

SearchDataManagement

Close