A faculty/staff/student team was used as a collaboration model to develop, maintain, and improve mobile applications built for use by students on the campus of California State University, San Bernardino. The team was developed in the software engineering class where the projects are mobile applications requested by real clients in the campus. After the class is over, the students continue the development through independent studies and senior projects. During this time, the students work with a team of student interns and staff from the Administrative Computing Services, Information Technology Division of the campus until the mobile applications are published in both Google Play and Apple App Store. The students learn tremendously through hands-on experience and actual interactions with real clients in the software engineering course. We found that the principles and concepts of software engineering are learned better in this project-based class.

It is difficult to teach students proper software engineering methodology in a classroom setting. Without hands-on experience, students may not understand why the software engineering process exists. By teaching students via a mock company experience, teaching software engineering can become a rewarding experience while showing the students how simple it is to follow the correct process. Here we show how in the microcosm of a mock software company it is possible to teach very real lessons about software engineering, unfamiliar technologies, teamwork and the realization that when a project ends, the code does not disappear.

This paper reports on our experience in achieving reusability and using component-based software engineering in the Algorithma 99 (Algorithm Animation) Project. We show how we extended and reused Algorithma 98 [2] into Algorithma 99 and how we prepared Algorithma 99 to be reused in Algorithma 2000 (to be implemented in Winter 2000). Component-based software engineering is not only confined to binary components, such as COM and CORBA, but is also applicable to software processes, architectures and design, and object-oriented libraries.

Article Free Access Share on The RMT (Recursive Multi-Threaded) tool: a computer aided software engineering tool for monitoring and predicting software development progress Authors: Arturo I. Concepcion Department of Computer Science, California State University, San Bernardino, 5500 University Parkway, San Bernardino, CA Department of Computer Science, California State University, San Bernardino, 5500 University Parkway, San Bernardino, CAView Profile , Sunny Lin Department of Computer Science, California State University, San Bernardino, 5500 University Parkway, San Bernardino, CA Department of Computer Science, California State University, San Bernardino, 5500 University Parkway, San Bernardino, CAView Profile , Scott J. Simon Environmental Systems, Research Institute, 380 New York Street, Redlands, CA Environmental Systems, Research Institute, 380 New York Street, Redlands, CAView Profile Authors Info & Claims ICSE '99: Proceedings of the 21st international conference on Software engineeringMay 1999Pages 660–663https://doi.org/10.1145/302405.302924Published:16 May 1999Publication History 4citation269DownloadsMetricsTotal Citations4Total Downloads269Last 12 Months38Last 6 weeks3 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

This paper describes Algorithma 98 which has three fundamental features: walkthroughs, animations, and availability of source code and documentation. The first two features allow the user to exercise the algorithm in a step-by-step manner while viewing its animation. The third feature makes Algorithma 98 an open system that can be improved and extended by another developer. This paper also describes the object-oriented software process that was used in developing Algorithma 98 to support its extensibility and reusability.

An object-oriented software life-cycle model, the Modified Spiral Model, was successfully used as the software process in the software engineering course in the Department of Computer Science, California State University, San Bernardino. The model lends itself quite naturally to the object-oriented approach of producing software systems in the iterative and incremental manner. The software engineering class is run like a virtual software company which is composed of teams and team leaders where performance is measured on being able to submit the software deliverables and the success of the task(s) assigned to the team. The paper reports on the implementation of the software project, Algorithma (Algorithm Animation), in the virtual software company using the Modified Spiral Model.

The paper presents an alternative way of having a hardware laboratory for the computer architecture course that is taught in every computer science curricula. For institutions like CSUSB, with no College of Engineering, having an actual hardware laboratory will be cost prohibitive. An alternative way is to have a set of computer-aided design (CAD) tools where students can design hardware and then test their designs using simulation. This has been done at CSUSB. By using MAGIC (a VLSI layout design tool) and IRSIM (a functional logic simulator) the VLSI Design Laboratory was developed for the computer architecture course in the Department of Computer Science. The VLSI Design Laboratory was implemented using the machines obtained from a matching equipment grant from IBM which consists of five IBM RS/6000s and 15 XStations. The paper presents how the laboratory complements the lecture and how the students learn the hierarchical design methodology of VLSI circuits. Future directions of the VLSI Design Laboratory are also presented.

A methodology is developed to map hierarchical, modular discrete-event models onto a distributed simulated architecture, the hierarchical multibus multiprocessor architecture (HM/sup 2/A). The proposed architecture contains features closely reflecting the structure, behaviour, and modular properties of the model being simulated. Hence, this approach improves on previous approaches, which impose the model on a predesigned architecture.>

A methodology is being developed to map hierarchical, modular discrete event models onto distributed simulator architectures. Concept developed for the first step of the methodology concerning model representation are discussed. The DEVS (Discrete Event System Specification) is extended to facilitate modular, hierarchical model specification. Procedures for top-down model development are expressed with the extended formalism and illustrated with a computer system model design.>