- 追加された行はこの色です。
- 削除された行はこの色です。
#contents
//** Week 1 Introduction [#e964045a]
//
//Hello everyone, my name is Yuji Shimojo and I'm 27. I am from Okinawa, Japan and live there now. My vitals are as follows.
//
//-- Proficient languages: Java, JavaScript, Visual Basic, SQL, Shell
//-- Moderate proficient languages: C, C++
//-- Less familiar languages: C#, Ruby, PHP
//-- Skills: Cloud computing, business development, requirements analysis, system architecture, database design, programming, system operational design
//-- Weaknesses: User interface design, English (second language)
//-- Certification: AWS Certified Solutions Architect
//-- IDEs: Eclipse (on Windows 7), Xcode (on MacOS X 10.6)
//-- Modeling tools: astah* community, ERMaster
//-- Version control systems: Subversion, Git
//-- Issue tracking: Redmine, Wiki (PukiWiki)
//-- Communication tools: Google Hangouts, Skype
//-- Private file sharing: Dorpbox, Box.net, Google Drive
//-- Documentation: Microsoft Office 2013 (on Windows 7), Google Docs, Google Spreadsheets
//
//I have more than 4 years of working experience as a technical sales representative. I directed of more than 50 projects including offering managed server hosting, cloud systems migration, integration, and 24/7 operational monitoring using cloud services such as AWS, and design/implementation/operations/consulting business/consumer applications for PC, feature phone, and smartphone/tablet as a technical consulting sales representative and a project leader.
//
//I enjoy architecting and building systems basically. Also, I have practical experience in proposing solutions for customers' business issues and analyzing system requirements for them in Japan, I am not exactly sure about business customs in the U.S. though.
//** Week 1 Introductions [#v9e5f82e]
//
//- Question
//
//When introducing yourself, create a new thread with your name in the Title.
//
//Since this class is so focused on a project, which you are asked to design and work on in a team, and since the backgrounds and interests of students tend to be quite varied, I am asking for considerably more information about each of your backgrounds. I have in mind using this information to form groups and suggest and approve appropriate projects.
//
//+ What CMSC classes have you taken at UMUC and/or other institutions? For UMUC, just the course number is enough, and please tell us the approximate course title for courses from other institutions.
//+ Same question about UMUC CMIS classes.
//+ Tell us a little about any industry experiences you have had.
//+ What programming languages have you used, and tell us you comfort level with each language:
//++ novice - got "hello world" equivalent running.
//++ beginner - a serious program using control structures (branching and looping) with a single function (main)
//++ competent - arrays and functions, implementing a design developed by others
//++ proficient - designed and implemented multiple classes, files, GUI's, threads, etc.
//++ expert - familiar with language specification, regularly guide others in using this language
//+ Same question about operating systems.
//+ Same question about software engineering topics:
//++ written programs designed by others.
//++ developed test plans
//++ developed detailed designs from conceptual designs
//++ developed conceptual designs from specifications
//++ developed system architecture from specifications
//++ elicited specifications
//++ developed work plans
//++ managed a software development project
//+ What technical magazines do you read, and how often?
//++ have heard of it
//++ read occasionally
//++ read regularly
//++ read every issue cover to cover
//+ What topic(s) would you like to explore in this class?
//+ Do you have some ideas for a software projects you would like to work on for this class?
//+ Anything else about yourself that you think is relevant to this class?
//
//That's a start, at least. I may think of other questions as we go along.
//
//I hope we have a great semester and get some rewarding experiences out of this class!
//
//Professor Nicholas Duchon (PND).
//
//- Answer
//
//Hello class, my name is Yuji Shimojo and I'm 28. I am from Okinawa, Japan and live there now.
//
//1. What CMSC classes have you taken at UMUC and/or other institutions? For UMUC, just the course number is enough, and please tell us the approximate course title for courses from other institutions.
//
//I took CMSC335, CMSC350, CMSC325, CMSC330, and CMSC412 in the past.
//
//2. Same question about UMUC CMIS classes.
//
//I took CMIS242, CMIS330, CMIS320, and CMIS435 in the past.
//
//3. Tell us a little about any industry experiences you have had.
//
//I have more than 5 years of working experience as a technical sales representative. I have much experience in technical sales for system migration, integration, and 24/7 operational monitoring by using both public clouds such as AWS and on-premise IT infrastructures including x86 servers, networking appliances, and storage hardware. Recently, as an AWS certified solutions architect, I am mainly directing projects including architecting, building, managing systems on AWS.
//
//4. What programming languages have you used, and tell us you comfort level with each language:
//
//-- Beginner: C#, Ruby, PHP
//-- Competent: JavaScript, Visual Basic, SQL, Shell, C, C++
//-- Proficient: Java
//
//5. Same question about operating systems.
//
//-- Client OS: Windows 7, MacOS X 10.6 / 10.11
//-- Server OS: Linux (CentOS)
//
//6. Same question about software engineering topics:
//
//My vitals related to software engineering are as follows.
//
//-- Skills: Cloud computing, business development, requirements analysis, system architecture, database design, programming, system operational design
//-- Weaknesses: User interface design, English (second language)
//-- IDEs: Eclipse, Visual Studio 2010/2015 (on Windows 7), Xcode (on MacOS X 10.6 / 10.11)
//-- Modeling tools: astah* community, ERMaster
//-- Version control systems: Subversion, Git
//-- Issue tracking: Redmine, Wiki (PukiWiki), Backlog
//-- Communication tools: Google Hangouts, Skype, Slack
//-- Private file sharing: Dorpbox, Box.net, Google Drive
//-- Documentation: Microsoft Office 2013 (on Windows 7), Google Docs, Google Spreadsheets, iWork
//
//In addition, I have practical experience in proposing solutions for customers' business issues and analyzing system requirements for them in Japan, I am not exactly sure about business customs in the U.S. though.
//
//7. What technical magazines do you read, and how often?
//
//I used to read tech magazines such as InformationWeek and Computerworld before, but I don't have much time to read them lately. Instead, I often read tech blogs related to AWS.
//
//8. What topic(s) would you like to explore in this class?
//
//I enjoy architecting and building systems by using various cloud services.
//
//9. Do you have some ideas for a software projects you would like to work on for this class?
//
//Although I don't have any exact ideas, I would like to integrate multiple cloud services and components.
//
//** Week 1 Discussion [#if96d194]
//
//- Question
//
//For this week's conference, respond to the following:
//
//-- Find an article in an IEEE or ACM journal about project management, read and summarize it, and give us your reactions to the article. Be sure to include a good citation to the article.
//-- What do you propose to do in case one or more members of your group make no significant contributions to your project.
//-- Note that reasonable ideas may be used in determining project grades!
//-- Describe some problems that might arise in a group project and suggest one or more strategies for dealing with those problems.
//-- You are welcome to comment (nicely!) on the postings of other students.
//-- I would suggest you consider the following reference -
//
//Hmmm - Typical web resource - it moved or died. - Check out stuff under the topic Resources (added Mar 18).
//
//I have attached a copy just in case the reference moves:
//
//-- http://faculty.weber.edu/cgjones/IST4730/SampleDeliverables/SoftwareProjectManagementPlan/ieee1058.pdf
//
//- Answer
//
//I chose the article Why Software Fails (Charette, R. N., 2005). This article is a little bit old, but even now I often hear that unfunctional and buggy business software costs too much.
//
//In my opinion, because there is no bug-free software, I suggest that you build of a management system that allows to detect and fix software bugs early. The same applies to hardware as well. You need to architect systems based on the idea of design for failure.
//
//In addition, you should try not to write code as much as possible, and make the very minimum of software. In other words, you actively use exist and mature software modules or components including open-source software and Web APIs.
//
//CENTER:Reference
//
//Charette, R. N. (2005). Why Software Fails. '''IEEE Spectrum,''' Retrieved on August 23, 2015 from http://spectrum.ieee.org/computing/software/why-software-fails
//** Week 1 Form Groups [#vd7d858c]
//
//- Question
//
//Here is where you discuss with each other topics you are interested in, and what role you would like to play in a project with the goal of forming at least tentative groups by the end of the week.
//
//By the end of this week, you should have pretty well decided on the project topic for your group, posted it here, and gotten my agreement.
//
//- Answer
//
//I would like to play a role as a developer or a systems architect. Because English is my second language, playing a leading role seems to be difficult for me.
//I have a project idea that is a building a Web scraping client app in in Java or Scala. The app allows you to automatically extract information in DOM or CSV from a website that requires you to log in with a username and password.
//
//As Luis posted my introduction to the Introductions thread, my skill sets are as follows.
//
//-- Proficient languages: Java, JavaScript, Visual Basic, SQL, Shell
//-- Moderate proficient languages: C, C++
//-- Less familiar languages: C#, Ruby, PHP
//-- Skills: Cloud computing, business development, requirements analysis, system architecture, database design, programming, system operational design
//-- Weaknesses: User interface design, English (second language)
//-- Certification: AWS Certified Solutions Architect
//-- IDEs: Eclipse (on Windows 7), Xcode (on MacOS X 10.6)
//-- Modeling tools: astah* community, ERMaster
//-- Version control systems: Subversion, Git
//-- Issue tracking: Redmine, Wiki (PukiWiki)
//-- Communication tools: Google Hangouts, Skype
//-- Private file sharing: Dorpbox, Box.net, Google Drive
//-- Documentation: Microsoft Office 2013 (on Windows 7), Google Docs, Google Spreadsheets
//
//I have more than 4 years of working experience as a technical sales representative. I directed of more than 50 projects including offering managed server hosting, cloud systems migration, integration, and 24/7 operational monitoring using cloud services such as AWS, and design/implementation/operations/consulting business/consumer applications for PC, feature phone, and smartphone/tablet as a technical consulting sales representative and a project leader.
//
//** Week 2 Project Plan [#y3ff10eb]
//
//- Question
//
//''Instructions''
//
//Your Project Plan should include an outline of the key milestones for your project and who will achieve them.
//
//''Requirements Specification:''
//
//What is this project supposed to do? Be as specific as you can
//The specification should include scenarios or Use Cases (HINT, HINT)!
//
//''System Specification:''
//
//Hardware and software base for your project.
//A PC with a JDK is reasonable, but you might add more details, or make other selections, as appropriate. For example you might specify a web server with PHP , or the Android SDK, Android Studio and a Genymotion emulator.
//
//Discuss the Project Plan and assign sections and responsibilities in your group. A group Discussion area will be posted early this week to facilitate your discussion. You should all submit a Project Plan to your Assignment Folder, but each group member should submit the same Project Plan.
//
//- Answer
//
//When we analyze software requirements, we have to analyze not only functional requirements but also non-functional requirements. Sometimes both software developers and customers tend to miss non-functional requirements when a software development project is initiated.
//
//Since it causes that we perhaps unintentionally have an enormous gap with customers, we want to consider non-functional requirements for our software development projects as well.
//
//Svensson et al. interviewed eleven companies which includes both B2B and B2C companies on software quality requirements. According to the article, prioritized types of quality requirements are different depending on whether software users are business users or consumers
//
//Figure 1: Importance of quality aspects in the article shows that usability is the highest prioritized quality aspect for consumer software. It is followed by performance requirements and stability. On the other hand, for business software, safety is the highest and it is followed by performance, reliability, and stability.
//
//As mentioned in the article, we can reference some common indications of non-functional requirements such as McCall's quality model and ISO 9126.
//
//CENTER:References
//
//Berntsson Svensson, R., Gorschek, T., Regnell, B., Torkar, R., Shahrokni, A., & Feldt, R. (2012). Quality Requirements in Industrial Practice-An Extended Interview Study at Eleven Companies. IEEE Transactions On Software Engineering, 38(4), 923-935. doi:10.1109/TSE.2011.47
** Week 1 Introductions [#xaf801e7]
- Question
Introduce yourself here by telling us your name, what part of the world you live, your major or primary area of study at UMUC and what you envision doing with your programming skills you obtain from this course.
- Answer
Hello class, my name is Yuji Shimojo and I'm 28. I am from Okinawa, Japan and live in Tokyo, Japan now.
I have more than 6 years of working experience as a technical sales representative and more than 2 years of working experience as an AWS (Amazon Web Services) certified solutions architect at an IT company based in Okinawa, Japan. I have much experience in technical sales for system migration, integration, and 24/7 operational monitoring by using both public clouds such as AWS and on-premise IT infrastructures including x86 servers, networking appliances, and storage hardware. Recently, as an AWS certified solutions architect, I am mainly directing projects including architecting, building, managing systems on AWS.
I'm currently majoring in Computer Science with a minor in Business Administration. I took CMSC335, CMSC350, CMSC325, CMSC330, CMSC405, CMSC412, CMIS320, CMIS330, and CMIS435 as part of my major in the past.
What programming languages I have used are as follows.
-- Beginner: Ruby, PHP, Python, Visual Basic, Shell, C, C++, C#
-- Competent: Java, JavaScript, SQL (MySQL, PostgreSQL)
What operating systems I use are as follows.
-- Client OS: OS X 10.11 El Capitan
-- Server OS: Linux (CentOS)
-- Local Virtual Environment: Vagrant and VirtualBox
My vitals related to software engineering are as follows.
-- Skills: Cloud computing (especially using AWS), business development, requirements analysis, system architecture, database design, programming, system operational design
Weaknesses: Front-end design and programming such as user interface design, English (second language)
-- IDEs: Eclipse, Xcode (on MacOS X 10.11)
-- Modeling tools: astah* community, ERMaster
-- Version control systems: Subversion, Git
-- Issue tracking: Redmine, Wiki (PukiWiki), Backlog
-- Communication tools: Slack, Google Hangouts, Skype
-- Private file sharing: Dorpbox, Box.net, Google Drive
-- Documentation: Microsoft Office 2016 for Mac, Google Docs, Google Spreadsheets, iWork
-- CMS: WordPress
In addition, I have practical experience in proposing solutions for customers' business issues and analyzing system requirements for them in Japan, I am not exactly sure about business customs and IT trends in the U.S. though.
** Week 1 Discussion [#a852eec6]
- Question
For this week's conference, respond to the following:
-- Find an article in an IEEE or ACM journal about project management, read and summarize it, and give us your reactions to the article. Be sure to include a good citation to the article.
-- What do you propose to do in case one or more members of your group make no significant contributions to your project. Note that reasonable ideas may be used in determining project grades!
-- Describe some problems that might arise in a group project and suggest one or more strategies for dealing with those problems.
-- You are welcome to comment (nicely!) on the postings of other students.
I would suggest you consider the following reference - I have attached a copy just in case the reference moves:
http://www.learningace.com/doc/2598322/1a75062f2077bdf9de0b36cd393068cc/ieee1058
- Answer
I chose the article Why Software Fails (Charette, R. N., 2005). This article is a little bit old, but even now I often hear that unfunctional and buggy business software costs too much.
In my opinion, because there is no bug-free software, I suggest that you build of a management system that allows to detect and fix software bugs early. The same applies to hardware as well. You need to architect systems based on the idea of design for failure.
In addition, you should try not to write code as much as possible, and make the very minimum of software. In other words, you actively use exist and mature software modules or components including open-source software and Web APIs.
CENTER:Reference
Charette, R. N. (2005). Why Software Fails. '''IEEE Spectrum,''' Retrieved on January 9, 2016 from http://spectrum.ieee.org/computing/software/why-software-fails
** Week 1 Form Groups [#q5cc2bc5]
- Question
Here is where you discuss with each other topics you are interested in, and what role you would like to play in a project with the goal of forming at least tentative groups by the end of the week.
By the end of this week, you should have pretty well decided on the project topic for your group, posted it here, and gotten my agreement.
- Answer
Hi class,
I would like to play a role as an AWS (Amazon Web Services) architect.
As I posted to the introduction thread, I have some experience in programming through UMUC coursework, but I actually have a little practical experience in programming, so that I am not so good at programming. Especially my weakness is front-end design and programming. Also, because English is my second language, playing a leading role seems to be difficult for me.
Instead, I can contribute for architecting and building back-end systems by using AWS because I have more than 2 years of working experience as an AWS certified solutions architect. I have certain knowledge about basic AWS services such as Amazon VPC, Amazon EC2, Amazon RDS, Amazon S3, Elastic Load Balancing, and Amazon CloudFront.
Although I don't have any exact ideas for the software project, I am interested in Infrastructure as Code such as configuration management by using Ansible, managing Amazon Machine Images (AMIs) by using Packer, provisioning AWS components (services) by using AWS CloudFormation or Terraform. I am also interested in serverless architectures on AWS such as using AWS Lambda (Node.js, Python, or Java), API Gateway, Amazon Cognito, Amazon DynamoDB, etc..
If someone is interested in building systems on AWS, I can prepare AWS accounts for each team member.
** Week 2 Discussion [#v3413b67]
- Question
For this week's conference, respond to the following:
-- Find an article in an IEEE or ACM journal about requirements analysis, needs assessment or specifications. Read and summarize the article, and give us your reactions to the article. Be sure to include a good citation to the article.
--- [[IEEE Computer Society - Premier Organization of Computer Professionals:https://www.computer.org/portal/web/guest/home]]
--- [[IEEE - The world's largest professional association for the advancement of technology:http://www.ieee.org/index.html]]
--- [[Welcome — Association for Computing Machinery:http://www.acm.org/]]
--- Access full text of these journals through the Library link in Tycho.
-- What are some important issues a project specification should address?
-- You might find outside references about project management and software engineering helpful. If you use them, please cite them.
-- You are welcome to comment (nicely!) on the postings of other students.
- Answer
I chose the article Requirements Engineering Tools (Carrillo de Gea, J. M., et al., 2011) which I found through the Library.
The authors surveyed requirements engineering (RE) tools in the world and evaluated 37 tools.
The evaluation is based on ISO/IEC TR 24766:2009: Systems and software engineering - System life cycle processes. The tools are assessed on the basis of elicitation, analysis, specification, modeling, verification and validation, management, traceability, other tool capabilities, global, and price range (single seat).
In my opinion, no matter what great IT tools we use, we are not necessarily maximize our performance essentially; however, adequate IT tools accelerates iteration speed and promotes collaboration.
I strongly agree with the author's opinion that selecting a RE tool is a key factor for such as distributed development teams and agile teams.
For distributed development teams, IT tools help them real-time communication and prevent miscommunication. For agile teams, the tools help them be less document-centric and more code-oriented.
Actually, our project team for the capstone project are using Slack for collaboration. We are able to actively discuss the project plan, specifications, and system design, and we also share code snippets to our Slack channel.
CENTER:References
Carrillo de Gea, J. M., Nicolás, J., Alemán, J. F., Toval, A., Ebert, C., & Vizcaíno, A. (2011). Requirements Engineering Tools. '''IEEE Software,''' 28(4), 86-91. doi:10.1109/MS.2011.81
** Week 2 Plans and Specifications [#fe87ac70]
- Question
This is where you should include an outline of the key milestones for your project and who will achieve them.
Get my comments.
Requirements Specification:
-- What is this project supposed to do?
-- Be specific.
-- The specification should include scenarios (HINT, HINT)!
System Specification:
-- Hardware and software base for your project.
-- A PC with JDK 6.0 is reasonable, but you might add more details, or make other selections, as appropriate.
- Answer
''What is this project supposed to do?''
This project is designed to allow a hospital to have a single enterprise system that ensures data needs only to be entered one time into the system. This will allow multiple departments to see relevant information, but only certain roles can modify certain fields. Additionally this will improve the efficiency of the hospital and reduce the number of errors.
''System Specification''
-- 2.5GHz processor
-- 1 GB of Ram
-- JDK version 8.0
-- Internet Connectivity
-- JSP/HTML/CSS/JavaScript as frontend
-- Servlet as backend
-- MySQL version 5.7
Case Scenarios:
++ Once going to the web interface for the system, the user will be prompted for a username a password.
++ Based on the role of the user administration forms, doctor forms, medical records forms will be displayed.
++ For administration forms the appropriate hospital employees can modify general information about patients, and staff members.
++ For doctor forms the doctor and the doctor’s team members are able to modify medical information.
++ For medical records the patient is able to review all general and medical information, but they will not be able to modify it.
++ Once the forms have been modified or reviewed the user clicks a save button which then sends all the inputted data to the database.
++ The database then timestamps the entry and saves the data in the appropriate fields.
++ Once all modification and reviews are done the user then clicks a log out button which securely logs the user off.
Milestones:
-- Design what the system is suppose to do and how different pieces fit together
-- Create database tables and fields
-- Create different front end modules and review front end code
-- Verify modules are translating data from front end modules to back end database
-- Test Wrong input values and verify the error correction is working
-- Put all modules together and test entire program functionality
-- Team Member Roles & Responsibilities:
Yuji Shimojo – Database lead, Backend development lead, Program reviewer
As database lead Yuji will design and implement the creation of tables and fields that hold all our patients data. Yuji will also verify that the data being sent to the database is correct, and ensure that the database is properly secured from traditional manipulation techniques. As the backend development lead Yuji will implement servlets with database connections. Additionally, Yuji will help review and make suggestions for other aspects of the project.
Cara Howie – Website design lead, Program reviewer
As the website design lead Cara will design, implement the front end interface that all the users will interact with. Cara will also ensure that the code has been designed to work efficiently, and that the code has been designed to prevent common manipulation techniques. Additionally, Cara will help review and make suggestions for other aspects of the projects.
Thomas Vera – Project lead, Technical writer
As project lead Thomas will ensure to keep up to date on group progress and any issues that will arises. Thomas will also provide any help in any area like designing test data and make suggestions for improvement. Additionally, Thomas will write all documentation for user guides, and manuals that will help troubleshoot any issues.
** Week 3 Discussion [#cb9f7e32]
- Question
For this week's conference, respond to the following:
-- Find an article in an IEEE or ACM journal about technical documentation. Read and summarize the article, and give us your reactions to the article. Be sure to include a good citation to the article.
-- You are welcome to comment (nicely!) on the postings of other students.
- Answer
Since I couldn't find an article relevant to "technical document," I searched a article in the UMUC library and chose Documenting Code: A Necessary Evil, or Just Plain Wrong? I'm a firm believer in comments—How about you? written by Otey, M. (2014).
This ariticle mentions how important documenting code is.
In my opinion, when you document code, it is very important that you define who readers at first. Even if you write instructions and procedures on how to do something in detail, if your comments have an entirely different expectation for your readers, it makes no sense. Additionally, it is important to write not only what the code do but why the code do so and also prior conditions if needed.
Nowadays, software documents are actually not only in MS Word or PDF formats but can be scripts themselves. For example, server configuration management tools such as Ansible and cloud provisioning tools such as AWS CloudFormation and Terraform can be the alternatives for build procedure manuals themselves. Also, most of modern ER diagram tools can generate DDL (Data Definition Language) statements. Furthermore, Swagger, which is a RESTful API framework, be specifications, codes, and documents in html for RESTful APIs. That allows us to minimize maintenance cost of software documents.
CENTER:Reference
-- Otey, M. (2014). Documenting Code: A Necessary Evil, or Just Plain Wrong? I'm a firm believer in comments—How about you?. '''SQL Server Pro, 16(4),''' 5-7.
** Week 3 User's Guide and Test Plan [#y948e766]
- Question
-- A detailed Test Plan + User's Guide.
-- Before the design!
-- Be exact about inputs and expected outputs.
-- This is the time to create test data files, if appropriate.
-- Feedback to the requirements documents - now is the time to make those clearer and writing a User's Guide as part of the test plan will help, also.
- Answer
** Week 4 Discussion [#p47bf873]
- Question
For this week's conference, respond to the following:
-- Find an article in an IEEE or ACM journal about the history of computing. Read and summarize the article, and give us your reactions to the article. Be sure to include a good citation to the article.
-- You are welcome to comment (nicely!) on the postings of other students.
- Answer
I chose the article Alan Turing and Bletchley Park (Severance, C., 2012).
This article is written about Alan Turing who is known as the father of modern computer science and mainly focuses on a highly developed mechanical computing device he designed at Bletchley Park, UK during World War II This cipher device was called the BOMBE and built to decrypt original German messages encrypted by the Enigma which was used by the German navy.
In addition to developing the BOMBE, Turing accomplished many of great achievements such as the Turing test, Turing machine, and Turing completeness; however, what he was not admired during his lifetime maybe because of his personality and absolute secrecy of the BOMBE project is indeed regrettable.
Interestingly, when I used to study at University of the Ryukyus, I learned that the ENIAC was the first general-purpose electronic computer through a computer history class at the college. I strongly remember that I was very excited when I had an opportunity to see actual panels of ENIAC at the Computer History Museum in Mountain View, CA in 2008. However, in doing searches for Alan Turing and early digital computers, I came to a conclusion that this is not necessarily true from a different point of view.
For example, Zuse Z3 which is an electronic computer developed in Germany, Colossus which is a subsequent decryption machine of the BOMBE, and the Atanasoff-Berry Computer (ABC) which is an electronic computer developed at Iowa State University, were built before the ENIAC started running.
Of course, they are not stored programs and may not be the von Neumann architecture, also Colossus is not general-purpose; however, since Z3 and ABC actually use binary numbers internally, they absolutely form the foundation of current computers.
CENTER:Reference
-- Severance, C. (2012). Alan Turing and Bletchley Park. '''IEEE Computer Society,''' Retrieved February 5, 2017 from https://www.computer.org/cms/ComputingNow/homepage/2012/0712/W_CO_AlanTuringandBletchleyPark.pdf
** Week 4 Design [#k4079e2f]
- Question
Design?
Classes, methods, fields, interfaces? Data structures, data file structures, input formats, output formats?
Overall approach.
Any relevant performance estimates would be appropriate here also.
This would be a good time to finalize test cases!
- Answer
** Week 5 Discussion [#g867d0ca]
- Question
For this week's conference, respond to the following:
-- Find an article in an IEEE or ACM journal about open source software, or division of labor. Read and summarize the article, and give us your reactions to the article. Be sure to include a good citation to the article.
-- You are welcome to comment (nicely!) on the postings of other students.
- Answer
** Week 5 Phase I [#afaec319]
- Question
The actual software, first of 4 phases. Start with "hello world", and at the end of each week, you should have something compiling and working.
This report should include the original milestone for this week, whether or not you are on schedule, any special problems that were encountered, and a reevaluation of the all the decisions made so far - from the very beginning.
Also, any changes to any of the previous documents should be noted.
- Answer
![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
