|
Order Reference
|
|
Q1
|
What type of business process is followed?
Our Business process:
- Offshore software development
- Project contract
- Lab agreement
- Onsite consulting service
|
|
Q2
|
What type of Application system is developed?
Ex: Back office Back office (Account, General affair, HR) Front office (Sales support system, Call center system, etc)
Back office:HRM system,Daily reporting system,Training system, Group scheduling management system,Employee and Remuneration management system, Business management system, Database productivity management system, Remodeling of distributed system
Real time communication system: Auto loom realtime monitoring system, Illuminometer management system, Using multiple anomalous information accessing software, Automated Tensile testing system
Note:For further details please refer the Company profile
|
|
Q3
|
Why do client develop software applications at offshore (India)?
- Inadequacy of soft skilled persons in Japan
- Value added process delivered by Indian companies.
- Expertise offshore development experience of India has attracted many American companies and has influenced in their success.
- Flexibility in upgrading to latest technology and providing native English communication skills.
- Skilled in providing Mathematical and logical solutions.
- Providing cost effective and Quality products.
|
|
|
Communication and review methods of document
|
|
Q1
|
How we share the information or requirements with the client?
- Short term business trip with detailed meetings are done.
- Client visits to India and explain the requirement to the team.
- Clients are communicated through secured sources (Ex: mails, Telephonic conversation and chatting etc)
- Prototype and description materials are created and are confirmed by the Clients.
|
|
Q2
|
How are each stage of development is reviewed?
Ex: Source code is read and revised while reviewing requirement specification in walk through sessions
- A walk through type of review is done. A prototype that is according to the requirement specification is developed and undergoes thorough testing.
- A source code review is made to maintain efficiency and Quality according to standards.
- Top down test is mainly carried out. The test is done based on the descending priority of the module.
- Dedicated testing team does Testing and validation of the program.
|
|
Q3
|
How frequently are the above mentioned reviews are carried out?
Depending upon the case, normally it happens to be once a week.
|
|
Q4
|
What are the review points of the above mentioned review?.
Review requirement specification
- Client's requirement is not misunderstood
- Emphasize 5W (WHY,WHAT,WHO,WHERE,WHEN)(5W)
- Documenting when there is a modification
Review External design
- The requirements are deployed with correct functionality
- At this point HOW is still theoretical
- Confirm that all the functionalities are covered
- Source code is checked for efficiency and proper deployment of functionalities
Review Internal design
- Are the functionalities implemented correct
- Go through all the logic path
- Is program structure and function splitting correct
Code reviewing
- Source code validation and readability
- Is it according to the coding standards?
- Code walk through
Reviewing Test planing
- Validate Test procedure and Test content
- Confirm that it covers the test cases
|
|
|
Development methodology
|
|
Q1
|
Which SDLC model is used in our company and why?
Waterfall SDLC model is followed. It is the most appropriate model for all business application
A spiral model is followed when the specification is tentative, and also when short deadlines. (Used when specified by client).
Prototype model is used when project demands for R&D and while migrating to latest technology.
|
|
Q2
|
Explain the recruitment estimation methodology.
The work needed for the project is identified (Work Breakdown Structure (WBS) is used), and an estimation based on man day for that work is done on the basis of pre-experience of previous project.
- Function point method(FP Method)
|
|
Q3
|
How do we progress through a project?
Requirement specification:Work schedule, Estimation QA table and work range document is done based upon the requirement specification.
External design:External design document, functional specification, Screen layout, Screen list, external connectivity, process flow, Table design document(Table list, ER diagram) output file list.
Internal design:Internal design document, Detailed functional document, program list, program process manual, Table design document (Table definition, Table relation document) Module structure diagram, function list.
Unit test certification, Q&A management sheet, Integrated Test certification, system test certification and user manual
|
|
Q4
|
At what stage, Project is outsourced and why?
It's any where between detailed designs to integrated testing.
Reasons:
- Itfs easy to handle in small modules.
- Business Know-How can be secured.
- It is necessary to set up a meeting to design an external design usually done at the onsite.
|
|
Q5
|
What kind of design documents do you demand from the client?
Requirement Specification, Functional specification documents
|
|
Q6
|
What type of design documents are created and delivered to the client?
Internal design document, Detailed functional specification, Program list, Program processing manual, Table design document (Table definition document, Table relation document), Module structure diagram, Test documents.
|
|
Q7
|
Incase of outsourcing is there any point to be noted when the specification is sent to the outsourcer?
- It is necessary to write the requirement specification or any other design document in detail.
- It will be of great help if there is abnormal case along with normal case.
- We make sure that the Specification sent is reconfirmed
|
|
Q8
|
Do you rely on a source code to analyze the existing software?
If so is it not difficult to understand a software with Japanese comment?
- Yes. Its helpful.
- There is no difficulty even with Japanese comments.
|
|
Q9
|
Is progress reporting done in terms of program?
What is the reporting duration?
Who creates the progress report?
- It's done on the clients wish but it is also done in terms of program and work schedule.
- Normally reporting is done in once a week.
- Normally progress report is created and managed by PM or PL who is in charge.
|
|
|
Maintenance period, Bug handling, Specification change policy
|
|
Q1
|
What is the maintenance durationH
In case of change in specification, Explain the standards of levying on the client when there is an addition of a requirement.
What is Bug handling policy?
- Maintenance period is for 1 year.
- Normally any change in the specification up to 5% is not levied. In case anything above that is done consulting the client
- Bug handling policy is as follows.
Priority 1 Serious bugs, bugs related to the operation of important functionality, bugs requiring immediate fixation 24-48hrs
Priority 2 Bugs requiring immediate fixation due important defect of individual functionality 24-72hrs
Priority 3 Appropriate modification of negligible defects of individual functionality 48-96hrs
Priority 4 Defects in the outlook is appropriately modified such that it satisfies the customer 72-120hrs
|
|
|
HRM policy
|
|
Q1
|
Generally, India has high rate of unemployment and what measure do you take to ensure the staff?
- Get interesting projects
- Provide stocks to employees
- Provide appropriate responsibility and necessary authority
- Provide an opportunity to learn latest technology
- Remunerations with health insurance and loans within the company for needy employees.
- Enthusiastic working environment
- Every employee is exposed to Japanese business culture and working environment.
- Provide a short term business trip to Japan
|
|
Q2
|
What are the criteria for employment?
Ex: Graduates, Experienced..
- Graduates, Fresher's and experienced
- People with future vision and flexibility are preferably employed
|
|
|
General
|
|
Q1
|
Why offshore projects to Nichi-in?
Merits:
- Skillful and efficient software development groups, Dedicated and experienced PL &PM's.
- Cost effective and value added service
- Competitive Quality
- Because of native English speakers and dedicated team for R&D we assure clients with latest technology.
- We provide logical and mathematical solutions for our customers.
- Time difference is less when compared to US.
- This time difference is used effectively.
- Japanese language has no barriers
- Our engineers have experience Japanese work culture
- Flexibility to deal with various aspects
|
|
Q2
|
Secrete for successful offshore development.
- Easing the barrier between the customer and vendor is must.
- Segregation of onsite and offshore work is necessary.
- Writing requirement specification and other design document in detail.
- A clear real time communication is necessary.
- Periodical follow up is must.
- Necessary to have a mutual understanding and aiming towards long-term partnership.
- Constant interaction between Client and engineers is must in order to provide a Qualitative product.
|
|
|
|
Office Location
|
Corporate Office:
Nichi-In Software Solution Pvt Ltd.
#813, 100 Ft. Ring Road,
Banashankari III Stage, Hosakerehalli,
Bangalore - 560 085, INDIA
Tel : +91-80-26720882 / 83 / 84
Fax : +91-80-26726861
|
|
|
