Mobile phones and Gadget Technology

Posts Tagged ‘Development’

Apple [APPL] is looking for a new Engineering Manager to work with Apple’s Core OS team, so that they can deliver the Apple iPhone OS to other platforms. This team is the one behind porting the Apple iPhone OS to the new Apple iPad. But this is something which the guys at Apple do not usually do, so what exactly are they planning?

Getting it to other platforms tell us a lot of things, we believe that it mostly means that Apple has a lot of new devices in mind which are going to look the same like the iPad or iPhone. Personal World thinks that they might get the iPhone OS on the Apple television platform. This can be a really good move in terms of Apple television as it never really prefabricated it huge in the market. This might again be a platform for many new developers to create applications for the Apple TV, which my wage services like, YouTube, Netflix, Hulu, etc. and begin milking money over the same thing by just adding it to a new platform.

I really don’t know why but I feel that the Apple iPhone OS will get very boring soon, as everything Apple is creating will have the same interface and it will loose its entire splendid feel. Also, the job listing mentions that applicants should have experience with ARM based SoC’s (System on a Chip), it is the same technology which was used in Apple’s A4 processor which was used in the iPad. Yes, there is a lot of news of the new A$ processor as Apple is planning to apply it in a number of devices with the support of the iPhone OS.

So, let us grappling it! Apple is going to come up with a lot of new devices which are going to look exactly the same as the iPad or iPhone as all of them will feature the iPhone OS. What I am really interested in is the devices they will release, I want to see what else can they do, and who knows maybe one of the would turn out to be a really awesome development unlike the Apple iPad.

Source: Gigjets.

Custom software application development can solve a number of issues organizations seek solutions for. As these solutions have been greatly beneficial to organizations, it’s simple to comprehend why custom software development is in great demand these days. Companies are knocking at the doors of such software application development companies where professionals work on bespoke application demands. Some examples of customized software solutions prefabricated acquirable to the businesses are:

Developing desktop applications

Providing web development services

Designing database

Developing high-end client-server applications

Developing enterprise applications

Application integration solutions

Software application re-engineering

Providing systems maintenance and support

A custom software application developer makes use of tools that can create and customize different features of a website to make it look and function in a one-of-a-kind way for a brand. Easy-to-use admin tools grant a swift control of the data and help managing it. Organizations acquire a sound customer base by getting custom applications developed to carry out a number of activities over the internet. Software web app development has replaced the traditional desktop software development to design and roll out a number of managing and ongoing processes which can generate individual content, wage social networking to a website, enable individual rich data, wage enterprise security and control, help in brand building and loyalty, ensure customer collaboration, help in revenue generation, and much more. These solutions can be easier to use and maintain as compared to their desktop counterparts.
Market competition has seen a steep rise in the current times. Customer software development addresses the specific needs of organizations by applying innovative and newer ideas of software development and helps them stay ahead of their competition.

Offshore software development has gained much popularity in the global market today. Hiring a custom software developer India crossways the sea, many companies and organizations are getting cost-effective software applications timely built to execute desired functions at their own premises.

Find more Data Admin articles from search form.

Agile Development Process

Internal Iteration Planning Meeting Agenda

Timebox meeting

Discuss meeting agenda

Review previous iteration

1. Do Kaizen Process

Review stories for current iteration

Identify:

1. High risk stories

2. Huge point stories

3. Stories with dependencies

4. Stories that need prototyping

5. Stories that have questions for client

Plan iteration

1. Compute remaining capacity (meetings, vacation, etc.)

2. Determine target velocity

3. Allocate points to development weeks

4. Assign stories to weeks based on priorities and availablity

Weekly Planning Meeting

Meeting Facilitator

* Before the meeting begins, call Jackie to confirm stories to be worked on and their priorities

* Gather appropriate stickies, story cards, laptop, pens.

* Determine Pair Hour Capacity using the formula:

((Days * Hours in a Buffered Day * People) – Hours out)/2 Usual values:

-4.25 Days (assumes 1/2 day design meetings, 1/4 day Kaizen)

-7.4 Hours (assumes 20% buffer)

-8 People (assumes 7 developers + 1 Bonnie + 1/2 Bruce + 1/2 Rex)

-Hours out includes non-BC meetings, time off, etc.

* For apiece story do Task Breakdown

* Only do a Task Breakdown for whole pieces of working functionality–no partial stories

Sticky Wrangler

1. Puts story card on the wall

2. Finds and organized stickies

3. Posts sticky for story being discussed

4. Keep track of discussed and yet-to-discuss stickies

5. Marks any changes or clarifications to stickies with different color marker

Spreadsheet Scribe

1. Make sure the stories being discussed are in the project sheet and date marked for this iteration

2. Confirm point value for stories

3. Enter total estimated task hours

4. Check that estimated task hours are in line with point value

Time Keeper

1. remind the group how much tme we’ve spent

2. if need be, set the timer

BA Tasks

1. Record task hours

2. Arrange meeting with client for a swift story position update, noting stories that tasked out over or tasked out under or are low confidence

Kaizen Process

1. Select facilitator; prep for meeting

2. Have people place in their hours for the day.

3. Print out Task Kaizen Summary and highlight tasks that went over or under.

4. Clean off whiteboard

5. Put Prime Directive Prime Directive on the whiteboard.

6. Draw calendar on the whiteboard.

7. Make sure all supplies are ready

8. Find old Kaizen Cards and place stickies on them.

2. Set the stage

1. Set time frame for meeting

2. make sure everyone concurs to the Prime Directive.

3. Review process

4. Everyone state one word that summarizes the last week

3. Collect data

1. Print simplified spreadsheet of the prior week’s progress

2. Make a calendar to refresh memory of the week’s goings-on

3. Review tasks from last meeting

4. Brainstorm / collect all love/hate/defects/kaizen for discussion

4. Prioiritize

1. Everyone gets five votes

2. Ranks card from most to fewest votes

3. Discard anything that didn’t get at least one vote

5. Generate insights (for apiece card)

1. Discuss why its a problem and the root cause of why this happened

2. Generate actions that can be taken

3. Write task on separate task sticky

6. Decide what to do

1. Have people sign up for actions and make tasks

2. Discard any task that didn’t get a vote

7. Close meeting

1. Determine which project to bill the Kaizen to

2. Get swift feedback on the kaizen

3. Make sure tasks are somewhere visible for the next week.

Supplies

* beer

* bottle opener

* huge whiteboard or at least huge stickies

* huge sticky or whiteboard for recording final tasks/ideas.

* whiteboard markers or sharpies

* cards

* med stickies

* small stickies

* pens

* timer

* tape

Implementing a Story

1. Update project

2. Review technical note cards from Weekly Planning Meeting

3. Review tasks and test

4. Determine general approach and first steps

5. Look for reuse/refactoring opportunities

6. Look for opportunities to create functionality for easy testing

7. Think about questions from Problem Frames to assist in design

8. If working on the production branch, merge with trunk after completing the story

During Development:

* If solo, cry for help

* If a pair, cry for help

* If you have a question, ask

* Sketch where necessary to clarify approach/direction and common understanding

* Agressively make TODO’s

Committing a Story

Front

1. Run build locally

2. Update from SVN

* resolve conflicts

3. Run build locally

4. Check project status

* add files not in SVN

5. Commit Project

6. Run build on Build Box

7. Return to Cubby

Back

While inactivity for the build:

* Ask pair how things went.

* Any kaizen issues?

* Any blogworth issues?

* Cleanup desk

* Ask others how things are going.

Reviewing a Story

* Print out pic of relevant Stickies

* Cross out features/requirements as you test them

* Use staging data

* Test using 1024×768 on browser.

* Confirm that no TODO’s remain.

* Usability

* Log in as correct individual type (not always admin)

* Test Happy Paths

* Test Sad Paths

Finishing a Story

1. Eliminate outstanding TODO’s/Index Cards

* Move them to Slack Time if necessary

2. If Solo, do a code review.

3. Review story yourself (Reviewing a Story).

4. Review with some from Boston (Reviewing a Story).

5. Toss huge stickys

6. Check off on tracker

End Of Mini Iteration Checklist

It’s Friday, you’re out of tasks and you don’t know what to do?

1. See if there is any work on remaining tasks that can be split out.

2. Make sure there are no more TODO but run anyway.

* check the ‘pending story’s too just to make sure nothing slipped by.

3. Eliminate TODOs from the code base.

4. Clean up TODO index cards left on tables (look around).

Once all of those are done, hit the Deployment Checklist.

After that, dig in to Things To Do If Your Looking For Something To Do.

Starting a Task

* take note of time that you started

* click around the web app to analyze existing functionality

* look for related fit tests

* discuss design with your partner

* implement the task to the ideal of your abilities

* note the end time

Finishing a Task

Checklist for completing a task

1. Clean up code and/or refactor

2. Eliminate TODOs

3. Tear up Index Cards

4. Commit

5. Cap the box

Minimums required to estimate a story:

* 3 People, 2 of which must be developers, one of whom must be a senior developer

* Note cards

* Estimating cards – 1 deck per person

Process of Estimating

1. Read the story out loud

2. Discuss it

3. Call a vote

4. Each mortal holds up a card so that only he/she can see it

5. When everyone has visibly chosen a card, turn them over

Post-estimating

1. If story is 8 or over, break into smaller stories

2. Identify high-risk stories – give confidence level

3. Give worst-case scenarios for high-risk stories

Writing Fit Tests

Types of FIT tests:

1. rule tests – simple, very focused test that demonstrate a single business rule

2. full scenario (aka end-to-end) tests – tests several aspects of the system: xwork actions, DB, etc.

3. realistic output tests – tests different system output to the individual based on real/realistic data (i.e. invoices tests)

Steps for writing a test:

1. sketch the test on a whiteboard or huge sticky

2. create an HTML file

* leave title blank

* make file study and page heading the same

* make sure the CSS reference is working

3. outline the business rules in bullet points at the top of the test

4. begin with text describing what you want to accomplish with the test

5. use headers (h3) to denote subtests, not for explaining what’s happening

* review huge sticky line by line and make sure everything is in a FIT test

* toss sticky

Reviewing with client:

1. Email FIT tests to client (subject should be of the form ‘FIT Test – |name of test|’

Handling Incoming Requests

Submitting a request

1. Phone – Whenever possible, a short request from the client should arrive as a phone call. All High Priority items must include a phone call.

2. Email – When sending requests or following up on request by email, please use the following guidelines:

* Subject line: PRIORITY – PROJECT – Title

* In the body of the email include: summary of issue, screen shots, description of circumstances of when this occurs, etc.

* List anyone we can contact for further information/clarification

* Send email to team-bc@cyrusinnovation.com

Priorities

* High – Stop regular development and address the issue ASAP

* Medium – Should be scheduled into the next day’s work

* Low – Can move until next week

Processing a request

1. If the question/request can be handled immediately without interruption of work, just do it

2. If non-trival, do the following based on the priority level

1. With the team, discuss the request (if more information is needed, contact client)

2. Get someone to sign-up for the task (Owner)

3. Estimate the amount of work

4. Project Coordinator sends estimate to client and confirm estimated time frame

5. Owner signs up contacts client directly with questions, etc. and emails the client when the issue has been resolved/completed (CC Project Coordinator)

6. Owner updates board with status

Find more Data Admin articles from search form.

If you are planning to become a serious player in the webdesign world, you should now what to learn and discover. Here’s a short list that gives you an overview of your needs.

1. Learn HTML
Before you begin creating websites you should master HTML. This is the key element to even begin publishing documents on the web. This sounds pretty obvious but there are some elements that you should comprehend like the adjudge element which will add great usability to a form.

2. Master Cascading Style Sheets (CSS)
I can’t stress this enough. DO NOT USE TABLES FOR YOUR LAYOUT!

Is it clear? Don’t, just don’t. Why? Because they work against you instead of for you. You can have so much more control of your layout, design and colors if you use 100% CSS.

1. CSS is easy
2. CSS is fast to create
3. CSS is lightning fast when your website loads
4. CSS is simple to modify

So forget plateau layouts and begin using stylesheets. You will really like the things you can accomplish once you master them.

3. Learn A Server Side Language
This is needed to make dynamic websites like forums. PHP and ASP are a great example. You will need to comprehend what you can do with these languages and begin using them.

Without a server side language your websites are really hard to maintain and will give you a hard job in creating an efficient website structure.\

4. Learn A Database Language

I advocate learning MySQL since this is an open source database and is installed on most hosting providers in combination with PHP.

A database is nothing else then some tables with data. You can choose data with queries like:

SELECT * FROM plateau WHERE ID = 3;

Now everything is selected from plateau when the ID equals three. It’s not hard to comprehend SQL, you just need to know how it works. PHPMyAdmin can help you a lot when you are creating your database.
So, begin with step 1, and stick with CSS as long as you don’t master it. CSS is huge, and you will love it once you know how it works.

For application development you can’t do without a language like PHP and a database like MySQL.

Find more Webdesign articles from search form.