Software engineers

The requiiements for scientific software development have continually increased. Besides the algorithmic core functionality, nowadays there is often a demand for a graphical user interface. In addition to the increasing importance of this visible component, which may still be seen as just an add-on, the software development itself has to fulfill stronger demands on software engineering requirements, such as maintainability and recoverability. 

HyperChem should not he viewed as a black box that computes on ly wb at its design ers th ougb L correct, tthasan open architecture that makes it possible to customize it many ways. As far as is possible, the parameters of molecular mechanics and semi-empir-ieal calculations are in the user s baruis. As the tech n ic ues of software engineering advance and onr expertise in building new... 

In order to balance public domain science with a high quality commercial software product it has been necessary for us to reimplement almost every aspect of computational chemistry embodied in HyperChem. All HyperChem source code is written in C or C-t-t, specified, designed, and implemented by Hyper-Chem s developers. We have stood on the scientific shoulders of giants, but we have not used their FORTRAN code Thus, although we have had access to MOPAC and other public domain codes for testing and other purposes, HyperChem computes MINDO, MNDO, and AMI wave functions, for example, with HyperChem code, not MOPAC code. We have made the effort to implement modern chemical science in a modern software-engineered product. 

Follow- Up. Even after the system is deHvered, additional work is usually needed. In conventional software engineering this is viewed as software maintenance or upgrade. It is referred to here as foUow-up to emphasize that the process of knowledge-base refinement that begias ia the prototypiag stage can continue even after the system is commissioned. The need for additional detail may come to light only after the appHcation has been ia use for some period of time. The time required to implement such enhancements should be takea iato accouat. 

Hughes, J. A. 1995 Ethnography, Plans and Software Engineering. In Proceedings lEE Colloquium on CSCW and the Software Process, Savoy Place, London, February. 

The team should have a wide range of knowledge and experience. If a contractor designs the plant, then the HAZOP team should include people from both tlie contractor and client organizations. On a computer-controlled batch plant, the software engineer should be a member of the HAZOP team, which should include at least one other person who understands the computer logic. 

One way of improving communication between chemical and software engineers would be to combine the jobs. There is a need for engineers who are equally at home in the two fields. 

Barstow, D., A perspective on automatic programming. In Readings in Artificial Intelligence and Software Engineering (C. Rich and R.C. Waters, eds.), pp. 537-539. Morgan Kaufmann, San Mateo, CA, 1986. 

The testing phase is important in expert system development. The practical applicability of the expert system will largely depend on this phase. Testing expert systems is different from normal software engineering in a number of ways. First, it is difficult to test exhaustively the full code and all possible paths the reasoning process may follow. Secondly, the nature of expert systems poses some typical problems. Due to their heuristic nature the correctness of the results cannot be easily verified. A certain degree of errors may be acceptable and, moreover, an... 

In this chapter we focus on implementation components executable code, source code, interface specs, code templates, and the like. In this context, a component is similar to the well-known software engineering idea of a module, although we have standards in place and technology infrastructure that makes building distributed component systems a reality. 

The goal of component implementation is to define an internal structure and interactions that satisfy the behavioral, technological, nonfunctional, and software engineering requirements for a component. In Catalysis the component specification (type) mentioned earlier identifies the behavioral requirements. 

Jacobson92] Jacobson, I., et al. 1992. Object-Oriented Software Engineering. New York ACM Press. 

JacksonD95] Jackson, D. 1995. Structuring Z Specifications with Views. In A CM Transactions on Software Engineering and Methodology, October, pp. 365-389. 

Jackson96] Jackson, M., with Pamela Zave. 1996. Where do operations come from A multiparadigm specification technique. IEEE Transactions on Software Engineering, 22(7) 508-528. 

Kurki-Suonio90] Kurki-Suonio, R., et al. 1990. Object-Oriented Specification of Reactive Systems. In Proceedings of the International Conference of Software Engineering. 

Luckham95] Luckham, D. C., J. J. Kenney, L. M. Augustin, J. Vera, D. Biyan, and W. Mann. 1995. Specification and analysis of system architecture using Rapide. IEEE Transactions on Software Engineering, 21(4). 

The OOram Software Engineering Method. Greenwich, CT Manning Publications. 

More companies are incorporating life-cycle costs and life-cycle assessment into their operations. The U.S. Air Force has developed a computer-aided software-engineering tool, for defining the complex sets of interacting activities in the life cycle of an aircraft. 

The primary differences, then, between development of expert systems and more traditional software engineering are found in steps one and two, above. First, the problems chosen will involve symbolic reasoning, and will require the transfer of expertise from experts to a knowledge base. Second, rapid prototyping, the "try it and see how it works, then fix it or throw it away" approach will play an important role in system development. 

Rated India s Most Admired Company by the Economic Times survey Opened offices in Germany, Sweden, Belgium, and Australia Established two development centers in the United States Established Domain Competency Group (DCG) and Software Engineering... 

R. S. Pressman, Software Engineering A Practitioner s Approach. McGraw-Hill, New York, 1987. 

Boehm BW. Software Engineering Economics. Englewood Cliffs, NJ Prentice-Hall, 1982. 

Charlette, RN. Software Engineering Risk Analysis and Management. New York McGraw-Hill, 1989. 

Gild T. Principles of Software Engineering Management. Reading, MA Addison-Wesley, 1988. 

Pressman RS. Making Software Engineering Happen. Englewood Clift s, NJ Prentice-Hall, 1988. 

---