Category: Engineering Homework Help

Choose a case study about a problem have been solved or they tried to solve it using the (Kamishibai board) and make a 9 power point slides about the case study.

the slides should include…

Title, Agenda, What is Kamishibai board, Application, Case Study, The results of the case study, References.

need to find reactions, deflected shape, axial force diagram, shear force diagram and bending moment diagram.Simple calculations and explanations needed

5.Go to this website and find the six images of clay particles. Then, answer the following questions:

https://www.researchgate.net/figure/SEM-images-of-…

Answer a-b-c

A. Read the figure caption. What is the name of the four clay minerals pictured (your answer should be four single words that end in ite).

B. Notice the clay particles in figure (a). This is the most common clay mineral. It is very important to note that although there appear to be 4 particles, there are actually 1000’s of particles. In fact, there are four ‘flocs’ (or groups) of particles. Each particle is actually very thin, and so, each floc is a stack of hundreds of particles held together like pages of a book (each page being a particle). What is the name of the force that is holding these particles together? Hint: reader…

C. Continue to explore figure (a). Notice the scale bar: 5 m. That is 5 micrometers, which is 0.005 mm. The width of most of the particles shown ranges between 1 and 5 m. The thickness of each particle, is, however, less than 0.1 m. The figure caption states “SEM images …”. What does SEM mean? In general, how does it work? Up to 5 sentences. Cite your references.

We will be using data visualization within a tool for this course. Please download and install R (CRAN) onto your PC.

There are two items that must be downloaded for this course: R and RStudio. Required!

If you are using a computer with a Windows operating system, make sure that when you download base R, you download Rtools, as well.

• Downloading R from the developer’s site
• Downloading RStudio Desktop (free version)

Verify this by attaching ONLY the screenshots to display your completion of the R software installation. Also, note (in one short paragraph- that is at least three sentences in length) how the installation went and if you encountered any issues. If you did, how were they solved?

Competency

In this project, you will demonstrate your mastery of the following competency:

• Implement a web service to enable an organizational need

Scenario

You are a business systems analyst at Web Explore, Inc. The company is planning to launch a new registration form on its website. Web Explore, Inc. now has customers in over 20 countries and data breaches are becoming more of a risk. Web Explore, Inc. has an organizational need to increase security and integrity of all data that is obtained through the form, such as customers’ names, email addresses, mailing addresses, and zip codes.

The new web service will meet these needs by:

• Allowing only customer sign-ups that have the @gmail.com domain
• Blocking non-@gmail.com domains and notifying the user
• Not duplicating customer email domains
• Using IP addresses to increase security
• Using recaptcha to reduce spam sign-ups

Since the registration form is a new web service that Web Explore, Inc. has never used before, its IT department has been asked by leadership to create a web service implementation plan. This plan will ensure that organizational needs are being met, and will inform leadership on how the task of creating a web service will be implemented effectively.

As a business systems analyst within the IT department, you have been asked to present this implementation plan. Your plan will include all aspects of the planning process for this web service.

Directions

Prepare a Web Service Implementation Plan for the new web service. Your plan should include the purpose, organizational needs, user experience, system architecture, tools and processes, data collection, and storage.

• Explain the purpose of the web service that is being implemented. Consider why the organization is implementing this specific web service.
• Describe how the new web service will enable the organizational needs listed in the scenario. Consider the needs that will be met once the web service is deployed and users engage with it.
• Explain how the user experience influences the implementation process. Consider how the user experience affects the interface of the web service.
• Illustrate the architecture of the web service by creating a diagram. Be sure to illustrate how the system functions. In your diagram, you must describe the importance of the interoperability of services.

You must create a diagram that includes at a minimum:

• Server
• Call and response packages
• Client
• Web service
• Describe the tools and processes that the organization will use as it implements this web service. You must consider:
• Equipment, including the hardware and software needed to implement the web service
• Personnel involved in the implementation of the web service
• Timeline—how long an implementation process would take
• Technical training—time and resources associated with training employees
• Identify how the organization plans to collect and store its user data. You must identify:
• The data that needs to be collected
• The data that needs to be stored
• The database that should be used, with a rationale for selecting that database that includes cost and efficiency

Overview

In this activity, your task will be to analyze the data and use the information gathered to answer simple questions by summarizing the results.

Prompt

Your team has been given various data sets in order to analyze information and summarize the findings. These are in the form of simple return merchandise authorizations, or RMAs. Your task is to write brief summaries that capture the results of the analysis to present to the product manager, who may or may not have a technical background. This is why you should write the summaries for an audience of nontechnical stakeholders.

Write a detailed summary of your analysis of the bulleted items below. Prepare your summary for nontechnical stakeholders. Use the list below to guide the structure and organization of your report.

• Write SQL commands that capture specific, usable data that can be used in your analysis.
• Analyze the results of queries to identify specific information that can be presented in your summary.
  1. Sales by region:
     1. Analyze sales by state to determine where the company has the largest customer base.
     2. Analyze the data to determine the top three products sold in the United States.
     3. Analyze the data to determine the top three products sold in the southeastern region of the United States.
        • Southeastern states to include in your analysis: Virginia, North Carolina, South Carolina, and Georgia
  2. Returns by region:
     1. Analyze the data to determine the top three products returned in the United States.
     2. Analyze the data to determine the top three products returned in the northwestern region of the United States.
        • Northwestern states to include in your analysis: Washington, Oregon, Idaho, and Montana
• Write an effective summary of the analysis of the captured data.
  1. Sales by region:
     1. Provide a well-written summary of your analysis on parts A through C.
  2. Returns by region:
     1. Provide a well-written summary of your analysis on parts A and B.
• Clearly communicate your findings to the Quantigration product manager by writing a report that explains your findings in a way nontechnical stakeholders will be able to digest and use.

In a Word document, use double spacing, 12-point Times New Roman font, and one-inch margins to write a report that captures your findings.

Overview

You have a job interview coming up with a prospective employer. They have given you the task of writing a summary that explains how you would write a report for one of their clients. They also want you to give a brief explanation justifying the approach you took.

Prompt

The potential employer would like you to conduct an analysis of data and then summarize your findings using clear language for a nontechnical audience. They have provided you with a data set called FleetMaintenanceRecords to base your report on for the interview. They have asked you to identify relevant themes that can be used to help them manage their fleet of trucks. In preparation for your interview, create an example summary of the analysis you conducted that you would use to communicate the findings to stakeholders. Place the deliverables for your instructor and the potential employer in the Analysis and Summary Template Word Document.

1. Analyze the data you’ve been provided to identify themes. Guiding information to gather:
   1. Review part-replacement frequencies and types and create a hypothesis that can be used by the fleet management team to better deal with vehicle maintenance. You’ll need to create a table called Parts Maintenance and load the data into it. Put this table in the database named after yourself. Load this data set from the ‘/home/codio/workspace’ path and run queries to find the results.
      1. Which parts are being replaced most?
      2. Is there a region of the country that experiences more part failures and replacements than others?
         1. Can you identify a region (Northeast, Southeast, Midwest, Northwest, Southwest) that has more reasons for replacement? Use the Region Definitions sheet PDF to identify states in each region.
         2. How might the fleet maintenance team use the information to update its maintenance schedule? Your response should be backed by the data you have found.
      3. Which parts are being replaced most due to corrosion or rust?
      4. Which parts are being replaced because of mechanical failure, like a flat tire or rock through the windshield?
2. Write a brief summary of your analysis that takes the information from step one and presents it in a way that nontechnical stakeholders will be able to digest.
3. Outline the approach that you took to conduct the analysis.
   1. What queries did you use to identify trends or themes in the data?
   2. What are the benefits of using these queries to retrieve the information in a way that allows you to provide valuable information to your stakeholders?
4. Lastly, identify how the functions in the analysis tool (Codio) allowed you to organize the data and retrieve records quickly so that they demonstrated what you wanted.

Place your responses in the template linked in the Prompt section. After you download the template, rename your copy by adding your last name to its file name. This will help organize your work once it has been submitted. 

Software Development Plan Document

This course is comprised of a series of individual project assignments that will also contribute to a group project due at the end of the course. Each week, you will complete a part of a software development plan, and you will share your results with your assigned group after your individual project has been graded. The group will integrate the projects into a group-developed version of the software development plan.

Your team will select a software engineering project that will cover the development process from conception to deployment. You are expected to perform the following tasks:

• Select a development methodology to plan a real-life application. 
• Perform a trade-off analysis covering quality, features, cost, and time for rapid development. 
• Conduct requirements elicitation and documentation for the application. 
• Prepare a systems component design. 
• Organize a schedule that covers build, integration, and test of the application. 
• Conduct a risk assessment for the project. 

Throughout this course, you will be working on a software development plan for the project that your team selects. You will not be developing the software, but you will work extensively with the concepts of good system-engineering practices during the creation of the plan. Additional information and the deliverables for each individual project will be provided in the assignment description for the project. The final deliverable is also known as the Final Key Assignment.

Project Selection

The first step will be to select a project as the target for your team’s software development plan. This project will be used as the basis for each of the individual project assignments throughout the course and should conform to the following guidelines:

• Nontrivial: The selected project should be large enough to allow reasonable exercise of the software development planning processes. 
• Domain Knowledge: Students in the team should be familiar enough with the organization or software category to allow focus on the planning tasks without significant time required for domain education. 
• Accessibility: Students in the team should have good access to the people and other information related to the organization or system because this will be an important part of the process. 

After your instructor has assigned team members, your team should select a software development project that fits these requirements and submit a proposal to the instructor before proceeding further with the assignments in the course. Approval should be sought within the first several days of the course. Your instructor will tell you how to submit this proposal and what notification will be given for project approval.

Assignment

For the assignments in this course, your team will not be implementing the actual development project, but rather, you will be developing a comprehensive software development plan document. Your team’s first task in this process will be to select a project to use as the basis of your plan. You will also create the shell document for the final project deliverable that you will be working on during each unit. As your team proceeds through each project week, you will individually and collectively add content to each section of the final document to gradually complete the final project delivery. Appropriate research should be conducted to support the analysis in your team’s plan, and assumptions may be made when necessary. 

Note: To be clear, each individual will be creating a software development plan in fulfillment of the individual project assignments, and the team will also create a software development plan in fulfillment of the group project due at the end of the course.

Team Project Deliverables

• Submit a project proposal to the instructor for approval. 
• After the individual projects are graded, team members should share their results with the team. The team should then integrate the results into the team’s version of the software development plan document. There is no submission for this part of the assignment until the end of the course. 

Individual Project Deliverables

• Software development plan document shell 
  • Use Word 
  • Title page 
    • Course number and name 
    • Project name 
    • Student name 
    • Date 
  • Table of contents 
    • Auto-generated TOC 
    • Separate page 
    • Maximum of 3 levels deep 
    • Fields of TOC should be up-to-date before submitting 
  • Section headings (create each heading on a new page with TBD as content, except for sections listed under new content below) 
    • Project Outline 
    • Development Methodology 
    • Requirements 
    • Design 
    • Development and Testing 
    • Project Schedule 
    • Risk Analysis 
• New content 
  • Project Outline 
    • Brief description of the project 
    • List of major issues to consider in the development of the application 
    • Material taken from approved proposal submitted to instructor 
    • Project must be approved by instructor 
  • Development Methodology 
    • Describe methodology that will be used for software development 
    • Include justification of selected methodology and why it suits project well 

• Summarize the scenario you would be dealing with as a software development example.
• Describe the development methodology you selected and why you think it fits well with the scenario.
• Identify the key strengths and weaknesses of the methodology.
• Discuss how you would deal with the potential problems that might arise from the weaknesses in the methodology. 

Responses to Other Students: Respond to at least 2 of your fellow classmates with a reply of at least 100 words about their primary task response regarding items you found to be compelling and enlightening. To help you with your discussion, please consider the following questions:

• What did you learn from your classmate’s posting?
• What additional questions do you have after reading the posting?
• What clarification do you need regarding the posting?
• What differences or similarities do you see between your posting and other classmates’ postings?

1st peer to respond to

For this course, the software development project scenario I recommend is planning a software project where a shopping management system will be developed. This development project is for clients who already have a successful physical store location; however, they want to branch out and open an online store as well. The online store will basically offer the same products as they offer in their physical location, plus other specialty items, but their products can now be available for people all over the United States. This one system will be the combination of many helpful management information systems such as Inventory control, Employee management, Management reporting system, Sales and Marketing, Accounting, human resource, databases, plus other necessary management information systems.

The integrated shopping management system will be a system that delivers a more convenient way to uphold the operations that take place to correctly manage an online store successfully. The system will need to be easy to use, understand, and navigate through, and security measures are required.

This shopping management system has a primary objective which is to adequately provide access to the tools that make overseeing the day-to-day operations of the online store a little easier and also helps with some of the day-to-day operations in the physical store location such as inventory control and employee management. The system should be fully equipped with features that can assist with maintaining the business aspects which will raise revenue, and customer satisfaction.

The software development methodology that is chosen to be used when developing a software application is crucial to the success of the project.

For this software development project, the methodology I believe to be the most appropriate is the Agile Development Methodology. I have a few different reasons why I believe this methodology is better to use when developing a shopping management system software application.

My first reason is because of the amount of teamwork that this methodology seems to make a requirement when working towards developing a software application. For the duration of the software project’s lifecycle, cross-functional teams work together to successfully design and develop the software they have been tasked with. Reason number two is how the processes of a software development project are carried out. What I mean by this is when using the Agile Development Methodology, incremental rapid cycles are used to develop software applications. Nonetheless, the project team continues to remain focused on delivering continuous improvements for the duration of the software project, along with ensuring the quality of the software by allowing modifications to be made to the software during any cycle or phase of the project. By developing the software in incremental cycles, fewer issues will emerge. Additionally, by allowing modifications to be made to the software, efficiency is fostered by the team.

The biggest reason why I think this methodology is best for a software project that is developing a shopping management system is that taking the agile approach when developing software means that the client, stakeholders, and even the end-users are more involved throughout the project and the development processes. The project team, client, stakeholders, and all others engaged to the project communicate daily. Everyone is kept up to date with the progress of the project.

As most things in life do, the different software development methodologies each come with their own distinctive advantages and disadvantages. However, they all share the same goal of offering a development process that meets the requirements of the stakeholders and the client and is conducted as efficient as ever. Some of the advantages and disadvantages of the Agile Development Methodology have been provided below.

ADVANTAGES

1. Incremental deliveries of the software product.
2. The feedback of the client, end users, and stakeholders are incorporated throughout the software project’s lifecycle.
3. New features can be experimented with.
4. Encourages frequent delivery of a software product in working condition.
5. There is the emphasis placed on people and interactions instead of processes and tools.
6. Communicating with all individuals which are somehow engaged with the project leaves less wiggle room to squeeze speculations into.
7. New products are being introduced to the market faster.

DISADVANTAGES

1. The roles of the team members are not well defined which can cause confusion between the members of the team.
2. Agile development is not suited for remote project teams due to the constant communication that needs to take place.
3. Inadequate resource planning.
4. Documentation is put together throughout/during the development processes not prior to. This can cause documentation to be a bit under-informed when it is actually put together.
5. If the requirements of the client are not clear, then understanding exactly what it is they are wanting is tedious.
6. Tracking the progress is difficult.

There is truly not one software development methodology that is perfect for all software projects around. The disadvantage of the methodologies helps make sense of that. But there are things that can be done to diminish the disadvantages.

Mitigating the agile development methodology disadvantages requires more of a Lean approach by emphasizing the importance of the following.

• Providing the client with software that is high in quality instead of providing them with a software product that is in a condition that functions.
• Managing a clear process for delivering the software product, not an uncertain route to be figured out along the way.

In an agile environment, risk management is built directly into the events of the project. The risks of a project when using the agile development methodology decrease as the project progressively moves forward. The way to ensure that the risks when developing software using this methodology are being managed in the correct way is nothing other than encouraging flexibility within the development processes. 

2nd peer to respond to

The scenario that I have chosen for my software development example is an Automatic Time Off system. For this software development plan, I will be using the Waterfall model as the methodology. The waterfall model is simple and very easy to use. In this model, each phase must be completed before beginning the next to avoid overlapping the phases.

The sequential phase in this model includes ?

• Requirement Gathering and analysis ? All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification document.
• System Design ? The requirement specifications from first phase are studied in this phase and the system design is prepared. This system design helps in specifying hardware and system requirements and helps in defining the overall system architecture.
• Implementation ? With inputs from the system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality, which is referred to as Unit Testing.
• Integration and Testing ? All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.
• Deployment of system ? Once the functional and non-functional testing is done; the product is deployed in the customer environment or released into the market.
• Maintenance ? There are some issues which come up in the client environment. To fix those issues, patches are released. Also, to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.

Each of these phases within the waterfall method are effective at promoting quality. If one of these phases did not exist within the waterfall method, my chosen application or system will most likely prove to be unsuccessful. The testing phase of the waterfall model is important because it discovers bugs and defects before the application is delivered to the client. Testing will guarantee the quality of the software and ensure it is reliable to use.

Without the maintenance phase, patches would not be released to fix the issues within the software or system. This phase includes obtaining maintenance requests from the end users and implementing these changes for a final product.

The disadvantages of using the waterfall model includes:

• Non-adaptive design constraints
• Working software is produced late during the life cycle, which will lead to high amount of risk and uncertainty.
• Not fitting for complex object-oriented projects (OOP).
• Poor methodology for long term and ongoing projects.
• Adjusting the scope during the life cycle can potentially end the project.
• Integration is completed at the end of the project; this does not allow to identify any challenges early in the life cycle.
• Waterfall methodology is not suitable for projects which contain requirements that have a possibility of changing.
• It is difficult to measure progress within stages.
• Reduces efficiency by not allowing process to overlap.

The advantages of using the waterfall model includes:

• Each phase will be completed before continuing to the next phase.
• Suitable for small projects where requirements are well defined.
• Quality and assurance testing is performed before the completion of each stage.
• Documentation is done at every phase.