2015年度 シラバス大学院 2015年度 シラバス大学院 2015年度 シラバス大学院
| 2016/02/01 現在 |
| 科目一覧へ戻る |
| 開講学期 ／Semester |
2015年度／Academic Year その他 ／Others |
|---|---|
| 対象学年 ／Course for; |
1年 , 2年 |
| 単位数 ／Credits |
5.0 |
| 責任者 ／Coordinator |
アレクサンダー ヴァジェニン |
| 担当教員名 ／Instructor |
アレクサンダー ヴァジェニン |
| 推奨トラック ／Recommended track |
－ |
| 履修規程上の先修条件 ／Prerequisites |
－ |
| 更新日／Last updated on | 2015/02/26 |
|---|---|
| 授業の概要 ／Course outline |
In modern complex applications reusability and interoperability of software components are of vital importance due to the increasing heterogeneous development platforms and variety of end user devices in which computational services need to be exposed. This led to the development of Design Patterns, which are means to encapsulate proven solutions to recurrent problems and they provide developers with a common language to abstract the logic encrypted under source code implementation structures. In this course we focus on the Model-View-Controller (MVC) design pattern that is very effective for human-centered software design. Students will study and work with the original Virtual- MVC design pattern that is an integration of MVC-design pattern and Service-Oriented Architecture. Our main contribution is to demonstrate the development process of re-usable components in the frame- work of the V-MVC pattern, through a development platform that supports Virtual-MVC based applications. |
| 授業の目的と到達目標 ／Objectives and attainment goals |
There are the following three scenarios of implementation of this Software Arena Project: 1. The concrete application can be assigned or selected together with the coach. After this, the team will make the application design based on Virtual-MVC decomposition and Service-Oriented Architecture (SOA). 2. Student/s can bring their own application that may be developed by other technologies. In this case, they can adopt this system to the SOA field. Accordingly, the comparison can be implemented of both variants. After finishing this course, student will have practical knowledge and experience in designing the SOA software, be able to formulate requirements and testing the software against these requirements. During the project, each of students will play and change his/her roles covering management activities, programming, testing and report writing. They will also evaluate and obtain the experience for both the user's and developer's perspective. |
| 授業スケジュール ／Class schedule |
Process Duration Products ------------------------------------------------------------- 1. Formulation of Requirements definition and specifications (2 months). 2. V-MVC decomposition (1 month) 3. Preliminary design, evaluation, correction requirements (3 months) 4. Software design, deployment and implementation (6 months) 5. Testing, Verification and Validation (6 months) 6. Result presentation, seminars, conferences (6 months) |
| 教科書 ／Textbook(s) |
Teaching materials will be prepared and handed according to necessity and features of concrete application. |
| 成績評価の方法・基準 ／Grading method/criteria |
Evaluation will be based on the reports & results obtained in each topic described. This is a team-based work, but contribution of each student will also be taken into account. |
| 履修上の留意点 ／Note for course registration |
It would be good to have experience covering the following undergraduate courses. a. Software Engineering I and II b. Distributed Systems c. Web Programming d. Java Programming I and II It is very important that student should have some practical experience in Java and Web programming, Databases, Algorithms and Data Structures. |
| 科目一覧へ戻る |
| 開講学期 ／Semester |
2015年度／Academic Year その他 ／Others |
|---|---|
| 対象学年 ／Course for; |
1年 , 2年 |
| 単位数 ／Credits |
5.0 |
| 責任者 ／Coordinator |
吉岡 廉太郎 |
| 担当教員名 ／Instructor |
サバシュ バーラ , 吉岡 廉太郎 |
| 推奨トラック ／Recommended track |
－ |
| 履修規程上の先修条件 ／Prerequisites |
－ |
| 更新日／Last updated on | 2015/02/27 |
|---|---|
| 授業の概要 ／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. |
| 科目一覧へ戻る |
| 開講学期 ／Semester |
2015年度／Academic Year その他 ／Others |
|---|---|
| 対象学年 ／Course for; |
1年 , 2年 |
| 単位数 ／Credits |
5.0 |
| 責任者 ／Coordinator |
吉岡 廉太郎 |
| 担当教員名 ／Instructor |
吉岡 廉太郎 |
| 推奨トラック ／Recommended track |
－ |
| 履修規程上の先修条件 ／Prerequisites |
－ |
| 更新日／Last updated on | 2015/02/27 |
|---|---|
| 授業の概要 ／Course outline |
ソフトウエア開発における品質の問題は、現在、ソフトウエア開発に携 わる全ての会社で発生しているといって過言でなく、経済紙等で言うと ころでの社会問題にもなっている。これを受けて、経済産業省では開発 プロセスのモデル策定や、ITスキル標準を規定したりする事で、改善に 取り組んできた。これらの実践論に基づく業界全体での開発の標準化は、 徐々に問題の解決に貢献しているものの、やはり、実際の問題解決とし てはこれら標準化を踏まえた、より実践的なプロジェクトマネージメン トスキルが必要とされる。 当カリキュラムでは、その習得方法として、 １．上流工程に当たる用件定義・設計から最終工程になる運用テストま での工程を一貫して経験し、決められた制限のもと、要求を到達するた めの方法論を構築し、各プロセスにおけるチェックレビューを行ないな がら、開発プロジェクトを実践する。最初に改善目標を設定し、終了時 に目標に対する到達度評価を行なう。 ２．開発するシステムとして、ソフトウエア会社の中で実際に使用する 基幹業務支援アプリケーションの構築を行なう。システムに関しては、 カリキュラム内にある要求定義により、後に受講者と決定する。通常の 業務支援システムではなく、コンポーネントの再利用と促進するための 基盤システムの構築のように、課題解決型・戦略投資型システムを構築 や、受注・請求管理のようなソフトウエア会社の全体像が展望できるシ ステムの構築を行なう。 ３．コーチや生徒同士が、ロールプレイをしながら、ユーザ側や開発側 になりきり双方の立場を経験しながら、開発プロセスを体験していく。 |
| 授業の目的と到達目標 ／Objectives and attainment goals |
当カリキュラムでは、業界標準的プロセス管理手法、スキル評価手法を 学び、その後に、実際のソフトウエア会社での総括的システム、ないし は、戦略的システムを、企画からテストまで構築し、当初策定した改善 目標に対しての到達度合いを評価することで、規範となるプロジェクト マネージャの育成する事を目的にする。 |
| 授業スケジュール ／Class schedule |
# 工程 期間 納品物 1 要求仕様 2ヶ月 要求仕様書 2 基本設計 1ヶ月 基本設計書 3 詳細設計 3ヶ月 詳細設計書 4 製造 5ヶ月 ソフトウェア 5 単体テスト 2ヶ月 単体テスト項目票及び成績表 6 結合テスト 2ヶ月 詳細テスト項目票及び成績表 7 システムテスト 1ヶ月 システムテスト項目票及び成績表 8 運用テスト 1ヶ月 運用テスト項目票及び成績表 |
| 教科書 ／Textbook(s) |
必要に応じ講義資料を配付する。 |
| 成績評価の方法・基準 ／Grading method/criteria |
各工程における成果物の評価する。 また、課題に取り組む姿勢や参加状況を考慮する。 |
| 履修上の留意点 ／Note for course registration |
関連する学部の講義（専修科目ではありません） a. ソフトウエア工学Ⅰ b. ソフトウエア工学Ⅱ c. ウェブプログラミング ・オブジェクト指向 ・ウェブアプリケーションの配備・運用 [ソフトウエア工学論] 会社での実戦経験があれば良いです。学生においてはソフトウエア工学Iの履修で構いません。 [JAVA、.NET等の開発技術] 上記いずれかの言語での開発を予定しています。言語習得が必要となります。大学での該当するカリキュラム履修、職場での経験で構いません。 [データベース] 技術習得されている事を推薦しますが、経験がなくとも可能です。必要に応じて関連する科目を履修してもらいます。 |
| 科目一覧へ戻る |
| 開講学期 ／Semester |
2015年度／Academic Year その他 ／Others |
|---|---|
| 対象学年 ／Course for; |
1年 , 2年 |
| 単位数 ／Credits |
5.0 |
| 責任者 ／Coordinator |
ヴィタリー クリュエフ |
| 担当教員名 ／Instructor |
ヴィタリー クリュエフ |
| 推奨トラック ／Recommended track |
－ |
| 履修規程上の先修条件 ／Prerequisites |
－ |
| 更新日／Last updated on | 2015/02/27 |
|---|---|
| 授業の概要 ／Course outline |
The role of the Internet as a tool to get knowledge and valuable information on different topics has been increased drastically over the past years. Studying and working with tools to access the information and knowledge on the web are the important part of software engineering education. Search engines allow users to retrieve information from the Web using keywords and phrases. Many words and phrases have multiple meaning. This is a big problem for search engines. Search engines provide the users with small snippets of texts taken from the retrieved documents. Users usually cannot evaluate the relevancy of a document using this information. One promising way to improve the quality of retrieval is to design summarizing methods and applications for Web-browsers which can run on client computers or on servers of Internet service providers. They will create automatically informative summaries for retrieved documents, and then present them to the end user. The aim is to reduce the amount of information to analyze manually. We propose the National Institute of Informatics, Tokyo, Japan and Saint Petersburg State University, Russia as project supporters. NII is a world leading organization in Information Access technologies applied to Asia languages. This institute is our partner in research related to information retrieval. Saint Petersburg State University is a famous university with excellent education traditions in mathematics, programming and software engineering. This university is our partner in the project on text mining. Both institutions can provide support via consultations by key researcher and practitioners, round table discussions, etc. These communications can be done via the Internet using modern communication technologies. NII can provide their data collections they use in NTCIR Workshops which are major scientific forums for researchers in the information retrieval area. |
| 授業の目的と到達目標 ／Objectives and attainment goals |
The goal is to create a prototype of the system helping scientists to search on the Internet for scientific information. The application software should run on mobile devices according to the following scenario: The application takes the user query, submits it to the search engine, gets its response, downloads top 10 documents, creates informative summaries, and presents results to the end user. The aim is to get the necessary knowledge in designing the architecture of software systems. |
| 授業スケジュール ／Class schedule |
a. Literature Study. Aim is to become familiar with the area of research and software development for mobile devices and to get the analytical skills necessary for any researcher and software development: This application area is very dynamic. b. Investigating software market. Aim is to find appropriate software components applicable to the area of research and to test new technologies designed for mobile devices. c. Implementing the classical summarizing methods and test them utilizing data collections created by NII. Aim is to see the base level of the quality of summaries produced automatically. d. Designing advanced methods on the base the latest results published in the journals and annual conferences such as TREC, NTCIR Workshop, SIGIR, WWW, etc. Aim is to design software components on the base proposed ideas. e. Conducting a set of tests to compare the quality of summaries designed applying classical and proposed methods. The aim is to select the most powerful method producing the best results. f. Designing the architecture of the application software running according to the aforementioned scenario. g. Programming the prototype of the system (creating code). The aim is to get skills to work in a team. h. Testing the prototype. The aim is to get knowledge about the full cycle of designing application software. |
| 教科書 ／Textbook(s) |
On-line documents will be used. |
| 成績評価の方法・基準 ／Grading method/criteria |
The final grade will be calculated based on the following weights: Presentations at group seminars ? 50% Software development ? 50% |
| 履修上の留意点 ／Note for course registration |
Prerequisites: Students have to have programming skills, be able to analyze the English scientific literature. Benefits: After implementation of this project, students will obtain the necessary skills to design, implement, and test the software system. They will get experience in designing WEB application software for mobile devices. This application area is growing very fast and the demand to design new software is very high. |
| 参考(授業ホームページ、図書など) ／Reference (course website, literature, etc.) |
Project Web site: http://web-int.u-aizu.ac.jp/~vkluev/courses/SEA/ |