Micro-business behavior patterns associated with components in a requirements approach

Macasaet, R. J.; Noguera, Manuel; Rodríguez, María Luisa; Garrido, José Luis García; Supakkul, Sam; Chung, Lawrence

doi:10.1145/2424563.2424573

Cited by 2 publications

(1 citation statement)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We characterize a micro-business based on the number of software components required in its prospective software system. The implementation of software systems requiring more than a small number of components (based on our industry experience, we made an informal estimate to be about 10 or so (Macasaet et al, 2012)) could increase the complexity of a project and the length of the software project (or man days required to complete the project), resulting in cost estimates that are out of range for micro-businesses. There would definitely be some exceptions to this estimation but these exceptions would be out of the norm.…”

Section: Introductionmentioning

confidence: 99%

Representing Micro-Business Requirements Patterns with Associated Software Components

Macasaet¹,

Noguera

Rodríguez

et al. 2014

International Journal of Information System Modeling and Design

Self Cite

View full text Add to dashboard Cite

This paper proposes representations for micro-business requirements patterns with associated software components. The patterns must be comprehensible enough for micro-business owners without technical backgrounds but at the same time be technical enough for the software developers who use them during the design and development of software. Both objectives are somewhat conflicting and trade-offs have to be made regarding their representations. The pattern representations use a combination of tables, business process models, goal graphs, labels, and UML component diagrams. First, the paper provides an example of a micro-business requirements pattern in the form of an inventory pattern and applies it in a real-world micro-business case, a clothes retail store. Through the example, it shows how the pattern is instantiated and associated with software components. Then, it shows how the patterns are applied in industrial practice, including the software development companies currently adapting and applying them, accompanied by observable strengths and weaknesses.

show abstract

Section: Introductionmentioning

confidence: 99%