
2017/01/30 |
Back |
開講学期 /Semester |
2016年度/Academic Year その他 /Others |
---|---|
対象学年 /Course for; |
1st year , 2nd year |
単位数 /Credits |
5.0 |
責任者 /Coordinator |
- - |
担当教員名 /Instructor |
- - |
推奨トラック /Recommended track |
- |
履修規程上の先修条件 /Prerequisites |
- |
更新日/Last updated on | 2016/01/18 |
---|---|
授業の概要 /Course outline |
http://www.u-aizu.ac.jp/en/graduate/it-specialists/features/ |
授業の目的と到達目標 /Objectives and attainment goals |
- |
授業スケジュール /Class schedule |
- |
教科書 /Textbook(s) |
- |
成績評価の方法・基準 /Grading method/criteria |
- |
Back |
開講学期 /Semester |
2016年度/Academic Year その他 /Others |
---|---|
対象学年 /Course for; |
1st year , 2nd year |
単位数 /Credits |
5.0 |
責任者 /Coordinator |
Rentaro Yoshioka |
担当教員名 /Instructor |
Subhash Bhalla , Rentaro Yoshioka |
推奨トラック /Recommended track |
- |
履修規程上の先修条件 /Prerequisites |
- |
更新日/Last updated on | 2016/02/01 |
---|---|
授業の概要 /Course outline |
Legacy information systems are typically the backbone of organizations and their failure can be crucial to their businesses. Legacy information systems can cause various problems since, for example, they usually run on obsolete hardware that is slow and expensive to manage, the software is developed using obsolete technologies that make integration with new systems and tracking of faults difficult, documentation and resources for maintenance are lacking. Several solutions have been proposed to these problems, such as, redevelopment, wrapping, and migration. However, given a concrete legacy information system, it is not always possible to rely solely on one solution. In every legacy information system problem, first an intensive study to find the most appropriate approach must be performed. Since this area of software engineering is relatively new, the numbers of practical experience reports of a comprehensive migration approaches are limited and sound methodologies do not exist. |
授業の目的と到達目標 /Objectives and attainment goals |
The aim of this project is to devise a comprehensive methodology for renovating a legacy system. An actual, mission critical legacy information system currently used in a relatively large organization will be considered. An intensive study to find the most appropriate approach for solving the organization's problem will be performed as well as research of existing knowledge in literature. A proposal of the methodology backed by analysis of risks and impact on business will be the output of this project. |
授業スケジュール /Class schedule |
Phase Duration Products 1 Analysis & study 2 months Anlysis report 2 Requirements spec. 1 month Requirements specification 3 Basic design 1 month Basic design report 4 Detailed design 3 months Detailed design report 5 Simulation 2 months Software, cost study report 6 Proposal prep. 1 months Renovation proposal 7 Methodology 2 months Research paper |
教科書 /Textbook(s) |
Textbook(s) will be specified as necessary. |
成績評価の方法・基準 /Grading method/criteria |
Evaluation will be based on the reports & results produced in each stage. Contribution of each student will also be taken into consideration. |
履修上の留意点 /Note for course registration |
This project is related to the following undergraduate courses. (These are NOT pre-requisites.) a. Software Engineering I b. Software Engineering II c. Web Programming d. Database Students are recommended to take the following courses from the educational curriculum a. Requirements Engineering b. Software project management *Software Engineering Prior job experience is favorable. For students, an undergraduate course on software engineering would be fine (Not a prerequisite but a strong recommendation). *Databases Corresponding knowledge and skills are recommended. If necessary, students will be requested to take corresponding courses or study literature. |
Back |
開講学期 /Semester |
2016年度/Academic Year その他 /Others |
---|---|
対象学年 /Course for; |
1st year , 2nd year |
単位数 /Credits |
5.0 |
責任者 /Coordinator |
Rentaro Yoshioka |
担当教員名 /Instructor |
Rentaro Yoshioka |
推奨トラック /Recommended track |
- |
履修規程上の先修条件 /Prerequisites |
- |
更新日/Last updated on | 2016/02/01 |
---|---|
授業の概要 /Course outline |
The quality of software development is a problem that all companies in the industry are facing and is considered a social issue by economic magazines and journals. The Japanese ministry of economics, trade, and industry has made efforts to formulate development processes standards and IT skill standards to introduce an industry standard for software development. Although these standard methods are helping to improve the situation, still practical project management skills are required to successfully run a project. |
授業の目的と到達目標 /Objectives and attainment goals |
In this curriculum, 1. Each student will experience all steps of a typical software development project, from requirements definition to final operational test. During the development, methodologies on how to fulfill requirements under strict restrictions, such as budget and time restraints should be established. Each process will be followed by a check review. 2. An application system to support core-business operations that will actually be used in a software company will be developed. Details of the system will be decided together with the students based on a partially predefined requirements specification. The system to be developed will be a problem solving or strategic investment type, such as a business support system that encourages reuse of software components. 3. Students will experience both the user's and developer's perspective of the development process through roll playing simulations with fellow students and coaches. |
授業スケジュール /Class schedule |
Process Duration Products ------------------------------------------------------------- 1 Requirements definition 2 months Requirements spec. 2 Basic design 1 month Basic design report 3 Detailed design 3 months Detailed design report 4 Implementation 5 months Software 5 Unit test 2 months Unit test report 6 Unification test 2 months Detailed test report 7 System test 1 month System test report 8 Operation test 1 month Operation test report |
教科書 /Textbook(s) |
Lecture materials will be handed out in class as necessary. |
成績評価の方法・基準 /Grading method/criteria |
Evaluation will be based on the reports & results produced in each stage. Contribution of each student will also be taken into consideration. |
履修上の留意点 /Note for course registration |
This project is related to the following undergraduate courses. (These are NOT pre-requisites.) a. Software Engineering I b. Software Engineering II c. Web Programming d. Object orientated Design Methods e. Web application deployment and operation Students are recommended to take the following courses from the educational curriculum a. Requirements Engineering b. Software project management c. Introduction to Advanced Internet Technology and Application *Software Engineering Prior job experience will be great. For students, an undergraduate course on software engineering will be fine (Not a prerequisite but a strong recommendation). *Development skills on JAVA or .NET The system will be developed by one of these languages. Basic knowledge and skills are required. *Databases Corresponding knowledge and skill are recommended. If necessary, students will be requested to take corresponding courses. |