The Making of Information Systems: Software Engineering and Management in a Globalized World

Pirmais vāks
Springer Science & Business Media, 2008. gada 24. apr. - 591 lappuses

Information systems (IS) are the backbone of any organization today, supporting all major business processes.

This book deals with the question: how do these systems come into existence? It gives a comprehensive coverage of managerial, methodological and technological aspects including:

  • Management decisions before and during IS development, acquisition and implementation
  • Project management
  • Requirements engineering and design using UML
  • Implementation, testing and customization
  • Software architecture and platforms
  • Tool support (CASE tools, IDEs, collaboration tools)

The book takes into account that for most organizations today, inhouse development is only one of several options to obtain an IS. A good deal of IS development has moved to software vendors – be it domestic, offshore or multinational software firms. Since an increasing share of this work is done in Asia, Eastern Europe, Latin America and Africa, the making of information systems is discussed within a global context.

No grāmatas satura

Lietotāju komentāri - Rakstīt atsauksmi

Ierastajās vietās neesam atraduši nevienu atsauksmi.

Atlasītās lappuses

Saturs

chap1pdf
1
chap2pdf
27
chap3pdf
95
chap4pdf
155
chap5npdf
235
chap6pdf
570
chap7pdf
570
chap8pdf
584
chap9pdf
643
Referencespdf
675
indexpdf
677
Autortiesības

Citi izdevumi - Skatīt visu

Bieži izmantoti vārdi un frāzes

Populāri fragmenti

208. lappuse - Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity, the art of maximizing the amount of work not done, is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective,...
208. lappuse - Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
208. lappuse - Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
207. lappuse - Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan...
207. lappuse - We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan...
586. lappuse - The application of knowledge, skills, tools, and techniques to project activities to meet the project requirements.
106. lappuse - A service is an abstract resource that represents a capability of performing tasks that form a coherent functionality from the point of view of providers entities and requesters entities. To be used, a service must be realized by a concrete provider agent.
176. lappuse - An interlocking set of automated techniques in which enterprise models, data models, and process models are built up in a comprehensive knowledge base and are used to create and maintain data processing systems.
570. lappuse - Program testing can be used to show the presence of bugs, but never to show their absence!
504. lappuse - Microkernel architectural pattern applies to software systems that must be able to adapt to changing system requirements. It separates a minimal functional core from extended functionality and customer-specific parts. The microkernel also serves as a socket for plugging in these extensions and coordinating their collaboration.

Bibliogrāfiskā informācija