Modeling in software engineering is not a new phenomenon. The basic tenets of software engineering process modeling include software life cycle management in terms of reflecting user-centered behavior, enhancing durability, and providing interactive user interfaces for better engagement. Models do provide the simulated ambiance for the architects, designers, developers, and users of the software as products and/or services to engage and rework until near perfect and useful behavior of the software is reflected. Over the years, abundant interventions have emerged in the software engineering discipline, including the unified modeling language, extreme programming, and user-centered designs supported by architectural artifacts and ontology. However, user interfaces have always remained a challenging area for architects, designers, and developers. The complexity of modeling to achieve desired user interfaces has grown manifold due to the ever-increasing demand for the seamless convergence of devices, software, communication media and modes, and user interfaces (for example, Internet of Things (IoT)). This dynamic situation in which issues related to applications, devices, interfaces, and front-end access raise the thresholds of quality, security, ease of use, and usability calls for better alignment among all these constituents (especially back-end and front-end). Therefore, modeling is perhaps the only way to provide durable results.

This book discusses primarily the interaction flow modeling language (IFML), a model attempting to bring convergence among content, interfaces, interactions, navigation, process logic, and presentations for the better roll-out of durable software services and/or products. It is a timely attempt to add value to software engineering process modeling exercises with a specific emphasis on establishing uniformity of the interaction style and usability of the interface. The book has been very systematic in approaching the modeling exercise by defining its belief systems (views, commands, content, and actions; effects) and then binding all these for better user interfaces. This book, in the process, has attempted to cater to the needs of professionals involved in the construction of interactive applications. These professionals include software designers, user interface design professionals, executives interested in information technology, and academia. The book with its supportive practical examples has enhanced readability and is quite useful for readers.

The book however, provides scope for improvements. The first is related to architectural treatments to the modeling exercise adopted through IFML. Discussions on the extant architectures, artifacts, and ontology in user interfaces and their comparative assessment with an IFML deliverable would have enhanced the readability and contributed immensely to the body of literature. The second is related to discussion on “cybernetics” in this important development of modeling. It is believed that models need to mature with proper cybernetics and user interfaces are related to this important phenomenon. In software engineering process models starting with system (software) development life cycles (SDLC) cybernetics, it is important to enhance the life cycles of products and/or services delivered. Architectural treatment of this aspect would have brought interesting dimensions to the overall modeling approach.

More reviews about this item: Amazon