Software Development Arena is a “super-project” with its internal program including the following tasks:
- analyzing a problem, corresponding application domain, and understanding requirements,
- designing software architecture, developing models and algorithms of components, and implementing or finding corresponding software for them,
- performing system debugging, experiments and usability tests for optimizing the design and getting results.
The tasks should be implemented by a team of 3-5 students. Each student should also understand a surrounding environment of the problem, including its network, hardware and software features. This activity is also oriented to gain project management skill and an understanding of the organizational issues.
The main goal of the project is in research and development of your application via the multi-purposed Programming Platform allowing integration of program and information components designed by different groups of developers. This platform is extending the MVC design pattern into a Virtual MVC for distributed applications taking in consideration other composite patterns for an efficient integration of the applications and services. The demarcation of a Functional (View) and an Implementation (Model) can be achieved deliberately by inducing an Integrator (Controller). The Controller can be enriched by encapsulating certain Non-Functional activities such as security, reliability, scalability, and routing. This enables the separation of Integration Logic from that of Functional Logic (Client Application) and Implementation Logic (Service). Advanced Mobile Networked Service devices (MSN-devices) are placed at the View level. The original MVC-design patterns and integration scheme will be involved including the following steps: 1). Design of stand-alone versions of sub-systems proposed, 2). Integrate them in the system using Dependency Injection Mechanism, 3). Improve software quality by cross-referenced components reusing, 4). Satisfy needs between team members. The client (View) part can be considered a ubiquitous multimedia device possibilities of which can me enhanced at the Model level. Special attention will be paid to the security issues. The other point of this project is in evaluating the V-MVC design toolkit in order to provide recommendations about its improvements.
Project implementation consists of several stages about six months each. If a student applied for the 1.5 years study then the project will have three stages. If a student studied two years then the project will have four stages.
Course books and materials will be provided during project implementation. The following books can be recommended to demonstrate application area:
1. Pocket PC Network Programming by Steve Makofsky, Pearson Education Inc., 2004
2. Mobile Computing by A.K. Talukder and R. R. Yavagal, McGraw-Hill, 2005
3. Software Engineering by Ian Sommerville, Pearson Education Inc., Ninth Edition, 2011
4. SOA Design Patterns by T. Erl, Prentice Hall, Indiana, US, 2009.
The presented course is intended for students who already have basic experience in programming such as C/C++ and Java Programming, Object-Oriented Programming, Software Engineering I and II. Some additional courses from the Graduate School Program can recommended according to the ability of team member and situation with the project implementation.
Project should be implemented by a team of 3-5 students. The team should prepare at least one report/documentation for each task. Each member of the team should make
1). at least two presentations at Research seminar to demonstrate research & development plans and results,
2). at least one presentation at Educational seminar to explain related work activity/papers.
WWW-site will be organized for the project team.
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.
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.
Process 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
Evaluation will be based on the reports & results produced in
each stage.
Contribution of each student will also be taken into consideration.
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 will be great. For students, an
undergraduate course on software engineering will 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.
ソフトウエア開発における品質の問題は、現在、ソフトウエア開発に携
わる全ての会社で発生しているといって過言でなく、経済紙等で言うと
ころでの社会問題にもなっている。これを受けて、経済産業省では開発
プロセスのモデル策定や、ITスキル標準を規定したりする事で、改善に
取り組んできた。これらの実践論に基づく業界全体での開発の標準化は、
徐々に問題の解決に貢献しているものの、やはり、実際の問題解決とし
てはこれら標準化を踏まえた、より実践的なプロジェクトマネージメン
トスキルが必要とされる。
当カリキュラムでは、その習得方法として、
１．上流工程に当たる用件定義・設計から最終工程になる運用テストま
での工程を一貫して経験し、決められた制限のもと、要求を到達するた
めの方法論を構築し、各プロセスにおけるチェックレビューを行ないな
がら、開発プロジェクトを実践する。最初に改善目標を設定し、終了時
に目標に対する到達度評価を行なう。
２．開発するシステムとして、ソフトウエア会社の中で実際に使用する
基幹業務支援アプリケーションの構築を行なう。システムに関しては、
カリキュラム内にある要求定義により、後に受講者と決定する。通常の
業務支援システムではなく、コンポーネントの再利用と促進するための
基盤システムの構築のように、課題解決型・戦略投資型システムを構築
や、受注・請求管理のようなソフトウエア会社の全体像が展望できるシ
ステムの構築を行なう。
３．コーチや生徒同士が、ロールプレイをしながら、ユーザ側や開発側
になりきり双方の立場を経験しながら、開発プロセスを体験していく。
当カリキュラムでは、業界標準的プロセス管理手法、スキル評価手法を
学び、その後に、実際のソフトウエア会社での総括的システム、ないし
は、戦略的システムを、企画からテストまで構築し、当初策定した改善
目標に対しての到達度合いを評価することで、規範となるプロジェクト
マネージャの育成する事を目的にする。
# 工程 期間 納品物
1 要求仕様 2ヶ月 要求仕様書
2 基本設計 1ヶ月 基本設計書
3 詳細設計 3ヶ月 詳細設計書
4 製造 5ヶ月 ソフトウェア
5 単体テスト 2ヶ月 単体テスト項目票及び成績表
6 結合テスト 2ヶ月 詳細テスト項目票及び成績表
7 システムテスト 1ヶ月 システムテスト項目票及び成績表
8 運用テスト 1ヶ月 運用テスト項目票及び成績表
必要に応じ講義資料を配付する
各工程における成果物の評価する。
また、課題に取り組む姿勢や参加状況を考慮する。
関連する学部の講義（専修科目ではありません）
a. ソフトウエア工学Ⅰ
b. ソフトウエア工学Ⅱ
c. ウェブプログラミング
・オブジェクト指向
・ウェブアプリケーションの配備・運用
[ソフトウエア工学論]
会社での実戦経験があれば良いです。学生においてはソフトウエア工学Iの履修で構いません。
[JAVA、.NET等の開発技術]
上記いずれかの言語での開発を予定しています。言語習得が必要となります。大学での該当するカリキュラム履修、職場での経験で構いません。
[データベース]
技術習得されている事を推薦しますが、経験がなくとも可能です。必要に応じて関連する科目を履修してもらいます。